News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

CB Crashes when trying to dock windows

Started by jeancf, November 18, 2008, 10:17:09 AM

Previous topic - Next topic

jeancf

Hi,

I am using C::B under Linux. When I try to dock a window (e.g. watches window) anywhere in the C::B application frame C::B crashes as soon as I release the mouse button.

When I start C::B at the command prompt I get the following error message after the crash:

The program 'codeblocks' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 727589 error_code 3 request_code 15 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.)
libxcb: WARNING! Program tries to lock an already locked connection,
        which indicates a programming error.
        There will be no further warnings about this issue.


My system:
Codeblocks SVN build 5312
WxWidgets 2.8.9 unicode
OpenSUSE 11.0
KDE 4.1.3

Thanks,

~/jc

Jenna

Quote from: jeancf on November 18, 2008, 10:17:09 AM
Hi,

I am using C::B under Linux. When I try to dock a window (e.g. watches window) anywhere in the C::B application frame C::B crashes as soon as I release the mouse button.

When I start C::B at the command prompt I get the following error message after the crash:

The program 'codeblocks' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 727589 error_code 3 request_code 15 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.)
libxcb: WARNING! Program tries to lock an already locked connection,
        which indicates a programming error.
        There will be no further warnings about this issue.


My system:
Codeblocks SVN build 5312
WxWidgets 2.8.9 unicode
OpenSUSE 11.0
KDE 4.1.3

Thanks,

~/jc

After a real long time, I found time to dig into it deeper and (hopefully) found a workaround for this bug, see here.