Code::Blocks Forums

User forums => Help => Topic started by: jeancf on November 18, 2008, 10:17:09 am

Title: CB Crashes when trying to dock windows
Post by: 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:

Code

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

Title: Re: CB Crashes when trying to dock windows
Post by: Jenna on November 11, 2009, 01:10:58 pm

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:

Code

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 (http://forums.codeblocks.org/index.php/topic,10831.msg78329.html#msg78329).