Hi
I have been running Codeblocks happily for over a year on my laptop but after some Debian upgrade it crashes with the following message:
"The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 13562 error_code 3 request_code 158 minor_code 3)
(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 have tried to debug it but without luck. I am using the build from Jen's repository (Thanks a lot Jens). Is the unstripped codeblocks binary in the packages or how can I compile the package with the debug binary?
Codeblocks only crashes on my laptop with Radeon video card (fglrx driver) and when I use kde4. If I switch to Gnome it works perfectly.
I do have three stationary computers with nvidia and some other video card and Codeblocks works without problems there under kde4.
I am using svn version 7899 but I have tried to downgrade it to version 10.05 but without luck.
I have also tried to create a new user and run Codeblocks but without luck.
It is most probably not a Codeblocks problem but the problem only shows up in Codeblocks. If you have any idea on what might be wrong, please tell me.
Regards
Gudjon
What exactly do you do before the crash occurs ?
Debugging should be able, if you install the debug packages (*-dbg*)
Hi Jens
Thanks for the answer.
It crashes at startup.
I did install codeblocks-dbg and tried to run
/usr/lib/debug/usr/bin/codeblocks
$ file /usr/lib/debug/usr/bin/codeblocks
/usr/lib/debug/usr/bin/codeblocks: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=0x663d20103b8b583ce316972a4d1211085466d581, not stripped
but it refuses to run
$ /usr/lib/debug/usr/bin/codeblocks
bash: /usr/lib/debug/usr/bin/codeblocks: cannot execute binary file
The same with gdb and I have tried to chmod a+rx on it.
Am I doing something terribly wrong?
Regards
Gudjon
The files in /usr/lib/debug just hold the debugging symbols, the executable is still /usr/bin/codeblocks .
If you start it with gdb, it should fetch the symbols from /usr/lib/debug/...
Hi Jens
Thanks a lot for the help, that explained it plus that I had to install libgtk2.0.0-dbg. Now I could break at gdk_x_error and got a hopefully useful backtrace. The backtrace is in an attachment but now I can do a decent bug report.
Regards
Gudjon