User forums > Help

crash: codeblocks wx2.6.1 unicode

<< < (5/5)

rickg22:
The "crash protection" is not an ugly hack,, is how things actually should BE in the first place.
The wxYield() inserted in the message manager _IS_ the ugly hack. (Do a revision graph on messagemanager.cpp, the wxYield shouldn't be there).

So I added the "hack" to precisely prevent errors like this from happening. Events triggered in the wrong time. Getting rid of the infesting wxYield's is much more elegant than adding SANITY_CHECK's all around the code (you can do a grep and see what i mean. That's an ugly hack, too!)

so, please test the crash on exit with the "crash protection" enabled... it gives me the info that I really need. Otherwise, we're getting lots of noise from the backtrace, and that ain't helping.

rickg22:
Heh. I found a double pointer deletion in my code... :P ironically, that was NOT causing the crash. I couldn't determine the cause!  :shock:  It must be somewhere in the wxWidgets code... but anyway, I found more or less what series of instructions triggered it. (Couldn't say which one exactly), and replaced the code with something much cleaner.

And doesn't crash now! :D

zieQ:
No more crash on exit for me, HEAD non-unicode wx2.6.1

grv575:
Yeah looks like questionable wxWidgets behavior - it still returns object memory that was already freed or something - those GetWindow() calls should have returned null instead of crashing when trying to call a method on the returned object.

tiwag:

--- Quote from: grv575 ---... those GetWindow() calls should have returned null instead of crashing when trying to call a method on the returned object...

--- End quote ---
no perfect world ...

Navigation

[0] Message Index

[*] Previous page