wxWidgets 2.6.1 weird crash

[Ceniza]

Ok, it seems like an internal error of wxWidgets. Could somebody else check if this happens too?

Oh, sure, what happens: Code::Blocks crashes (tested with Code::Blocks CVS 29-Jun-05 and wxWidgets 2.6.1 under Windows with GCC 3.4.4).

Ok, I'll be a bit more specific.

I'ven't found the exact way to reproduce it but it has to do with the toolbar.

Open Code::Blocks. Ok, good, it loaded. Now start moving the mouse pointer side to side, left to right and right to left, over the toolbar. If it hasn't crashed yet try opening a project and continue moving the mouse over it. At some point it'll crash, at least here.

The backtrace looks like this:

Program received signal SIGSEGV, Segmentation fault.
0x10178a4a in wxToolBar::FindToolForPosition ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
(gdb) bt
#0  0x10178a4a in wxToolBar::FindToolForPosition ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#1  0x101795d7 in wxToolBar::HandleMouseMove ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#2  0x101796fb in wxToolBar::MSWWindowProc ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#3  0x10109e20 in wxWndProc () from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#4  0x77d18709 in USER32!GetDC () from D:\WINDOWS\system32\user32.dll
#5  0x009b05a0 in ?? ()
#6  0x00000200 in ?? ()
#7  0x00000000 in ?? () from
#8  0x000a0395 in ?? ()
#9  0x10109de0 in wxWindowCreationHook::~wxWindowCreationHook ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#10 0x77d187eb in USER32!GetDC () from D:\WINDOWS\system32\user32.dll
#11 0x10109de0 in wxWindowCreationHook::~wxWindowCreationHook ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#12 0x77d189a5 in USER32!GetWindowLongW () from D:\WINDOWS\system32\user32.dll
#13 0x00000000 in ?? () from
#14 0x10109de0 in wxWindowCreationHook::~wxWindowCreationHook ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
#15 0x77d1bccc in USER32!DispatchMessageA ()
   from D:\WINDOWS\system32\user32.dll
#16 0x0022fc80 in ?? ()
#17 0x00000001 in ?? ()
#18 0x0022fc18 in ?? ()
#19 0x100e9775 in wxEventLoop::ProcessMessage ()
   from D:\WINDOWS\system32\wxmsw26_gcc_custom.dll
Previous frame identical to this frame (corrupt stack?)

Nasty, eh?

I tested with another program which also has a toolbar and couldn't get it to crash. Who knows, at the end it could be a problem with a widget of Code::Blocks that gets Destroyed or something.

[Ceniza]

Ok, got to track it down.

The problem is related to the GDB plugin.

The whole toolbar works just fine, doesn't matter where the mouse pointer is on, but if I move it over one of the tool buttons created by the GDB plugin it crashes.

I'll try to take a look at it. Seems like an unitialized pointer.

[Ceniza]

Ok, after a few hours trying to find the bug it seems like there's no spoon, er... bug in the GDB plugin.

I reconsidered the fact of it being a wxWidgets 2.6.1 bug and it really seems to be now. Anyone using that version is encouraged to patch it http://ftp://biolpc22.york.ac.uk/pub/2.6.1/wxWidgets-2.6.1-Patch01.zip (that link is from www.wxwidgets.org).

I'll patch mine, recompile wxWidgets, recompile Code::Blocks and will be commenting here about it (I'll edit this post).

[edit]
Well, that crash is gone but a new one arrived  

Now Code::Blocks crashes on exit but only when the Code Completion plugin is enabled and it really seems to blame Code::Blocks this time.

Time to hunt another bug...
[/edit]

[rickg22]

Try closing codeblocks _AFTER_ the debug log shows that all the files have been parsed. I hope it's not what i fear, but i'm afraid that the "crash on early exit" bug has returned... :shock:
(cue horror music chords)

[frog-o]

i would sugest trying to compile with gcc version 3.3 I have read people have problems with gcc 3.4 for some projects.  One such project is orge, read the readme in the dev-cpp package in the ogre dir after it is installed.   I know that on autopackage.org in there Packager QuickStart guid they say that the abi was broken again in 3.4 and think it has more problems then that.  I not sure what mingw package that would be thou.

[frog-o]

sorry for my post it make no sence just ignore it i relly need to read thing more before posting

[DreadNot]

Any more on this?
I also get crashes using wx2.6.1.
It seems to crash when I do absolutely nothing sometimes.
There must be some background thread causing the problem.

[rickg22]

the only place where we use background threads is in the code completion plugin. Try disabling it and keep testing.

[mandrav]

Any more on this?
I also get crashes using wx2.6.1.
It seems to crash when I do absolutely nothing sometimes.
There must be some background thread causing the problem.

Have you applied the patch posted above?

Yiannis.

[DreadNot]

As per my post in Incompatabilities between wx2.4 and wx2.6, the crashing seems to have disappeared.  I believe the wx2.6.1 patch fixed the problems as well as the updated code from CVS.

Also, it dosn't seem to crash on exit from the debugger either--things are looking good!   

Sorry, I haven't been around lately.