[BUG] Crash after reporting LOOONG compiler errors

[Commodore64]

On Linux (Kubuntu 7.04) when the compiler produces a very long error string, such as the one in the screenshot, C::B crashes almost immediately. The screenshot was taken just a while before the crash!

This is what I get in the command line:

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 171964 error_code 11 request_code 53 minor_code 0)
  (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.)

I'm using the latest nightly build, but I've had this problem since I installed C::B on Kubuntu (a couple of months ago). On windows everything seems to work fine.

Thank you, and here it is the screenshot.

[Commodore64]

Same kind of crash, with the same error, occurs when using the debugger  :?

[MortenMacFly]

I'm using the latest nightly build, but I've had this problem since I installed C::B on Kubuntu (a couple of months ago). On windows everything seems to work fine.

A piece of code with an error that produces such a long message would be of much help... I don't know how to do so - I don't develop errors... ;-) Can you provide such?
With regards, Morten.

[Commodore64]

A piece of code with an error that produces such a long message would be of much help... I don't know how to do so - I don't develop errors... ;-)

:lol:  :lol:  :lol:

Unfortunately I cannot right now... it is a large library that has not been publicly released yet.

Anyway, I've made a new finding right now. As a gtk+ theme, I was using "Qt" (i.e. the gtk to qt "converter", which is the default gtk+ theme in kubuntu). If I use a "normal" gtk+ theme, instead, the bug disappears. Thus possibly it is not a C::B issue...

Thank you,
Luca

[rickg22]

There is a way to generate such a long error. Use the #error precompiler directive.