Crash on startup if mouse clicked too early (Debian packaged 10.05)

[rogerjames99]

Has anyone else noticed this. Using the debian packed 10.05 version of Code::Blocks if you do almost any keyboard/mouse interaction after codeblocks has started but before the code completion toolbar has updated itself, Code::Blocks crashes.

Is this a known problem? Is there a workaround other than just remembering to be patient?

I wonder if this could be related to running on a quad core processor.

Roger

[oBFusCATed]

C::B runs fine on quads...

Please installed the -dbg package (I think there is one provided for debian) and then run "gdb codeblocks",
when you get a crash execute the "bt" command and paste the output of it here (please use [ code ] tag).

[Jenna]

You can also look if there is a crash-report in /tmp/codeblocks_dbgrpt-[pid]-[date]/ , it should be named codeblocks.xml.
You can attach it here (after renaming it to txt or zipping it).

[rogerjames99]

I could not find  an xxxxxxxx-dbg package in the Debian repositories. I searched on "codeblocks" using synaptic.

As you might expect, when I actually try to reproduce the problem it does not appear very easily! However I did manage to get to one crash just by clicking in one of the source windows immediately on startup. I then checked in the /tmp directory and found a number of dbgrpt directories including one with the correct time date stamp. However all of them are empty!

For information crash I got was when I had been trying a few times with one .cbp file and then switched to a different one. I do not know if this would mean that some sort of cache was being recreated.

Sorry

Roger

[oBFusCATed]

See the packages on the download page of C::B: http://www.codeblocks.org/downloads/26

[Jenna]

I could not find  an xxxxxxxx-dbg package in the Debian repositories. I searched on "codeblocks" using synaptic.

Where did you get the files you have installed ?

Code::Blocks is not on official debian repo.

You can use either the packages from our download-page as mentioned by oBFusCATed, or use my repo to install a nightly (see http://apt.jenslody.de/ for details).

Debug packages can be found at both places.

[rogerjames99]

Oops, my bad. I had forgotten that I had downloaded the original packages from berlios rather than the debian repositories.

Roger

[rogerjames99]

Ok, got a stack trace now.

Code

(gdb) bt
#0  0x00000000 in ?? ()
#1  0xb6b7248e in wxEventPtr::~wxEventPtr () from /usr/lib/libwx_baseu-2.8.so.0
#2  0xb6b72bf1 in wxEvtHandler::ProcessPendingEvents ()
   from /usr/lib/libwx_baseu-2.8.so.0
#3  0xb6ad3e51 in wxAppConsole::ProcessPendingEvents ()
   from /usr/lib/libwx_baseu-2.8.so.0
#4  0xb6deae9f in wxAppBase::ProcessIdle ()
   from /usr/lib/libwx_gtk2u_core-2.8.so.0
#5  0xb6d3e2e5 in ?? () from /usr/lib/libwx_gtk2u_core-2.8.so.0
#6  0xb6296291 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x00000000 in ?? ()