User forums > Help

Crash when debugging

(1/2) > >>

xplodwild:
Hi everyone,

I recently noticed a bug. When my app segfault in debug mode, C::B switch to debugging layout, but then crashes immediately with a X Window System error (BadAlloc). I tried 8.02 and latest SVN build (21 june), same problem happens. I'm running Ubuntu 9.04, and tried xserver-xorg 1.6.0 and 1.6.1 and same problem happens with the two.

What to do ?

oBFusCATed:
Can you show the crash report or a backtrace or even a simple test project that reproduces the bug?

xplodwild:
All I see in the console before the crash is :

Switching to debugging layout

The program 'codeblocks' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 788 error_code 11 request_code 145 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

It happened in a singleton class in a constructor, because the vector wasn't sized correctly. I can't reproduce the bug alone, maybe it's related with other things (my project is composed of nearly 40 files, and most of them are opened simultaneously).

Edit: It appears that it crashes when I open the Call stack window.

oBFusCATed:
Please run codeblock inside gdb:

$ gdb codeblocks
gdb$ run
crash C::B
gdb$ bt

and paste the output

edit:
if the backtrace does not contain meaningful information you should use C::B compiled with debug info in it

Jenna:
We had such a behaviour about one and a half years before (it was in fact a xserver-error).

It has most likeley not the same cause, but nevertheless it might be worth a try:

http://forums.codeblocks.org/index.php/topic,7661.0.html

Navigation

[0] Message Index

[#] Next page