find details in order to report a crash
lazarus / 1-Linux

----------------------------------------------------------------------
FangQ · 2009-08-18 15:48

I have been using Lazarus for half a year on a couple of linux boxes
and generally I am very happy with it.

In the past, I have been using 0.9.26-{2,4} on Ubuntu and CentOS. I
had some troubles loading forms in lazarus: the layout always changes
for the next loading, some components, such as Toolbar and panels that
have alTop/alBotton alignment always came out funny (either have 0
height or much taller). Recently I upgraded to the nightly-build,
0.9.27 series, the default gtk2 backend seems more reliable in keeping
the layout of the forms. However, occasionally, I experienced crashes,
roughly once or twice a day.

When it crash, it prints messages as following

Code: [Select]The program 'lazarus-ide' received an X Window System
error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such
operation)'.
  (Details: serial 8670407 error_code 1 request_code 0 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.)
The program 'lazarus-ide' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such
operation)'.
  (Details: serial 8670410 error_code 1 request_code 0 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 want to give some useful feedback to the Lazarus developers so that
this problem can be debugged. However, I don't know if the above
message is sufficient. If not, where can I find more detailed cause of
the crash?

thanks

----------------------------------------------------------------------
Marc · 2009-08-19 10:38

unfortunately these kind of errors are very hard to debug, even if
they can be reproduced.
The info provided by x or gtk is too common to do anything with it.
The best thing to solve this is to report how it can be reproduced.
if not then you might have success with reporting the location by
running lazarus inside gdb:
gdb lazarus
> set args --sync
> br gdk_x_error
> r

when gdb breaks:

> bt

to show a backtrace.

----------------------------------------------------------------------
FangQ · 2009-08-19 14:44

thanks! I will give it a try next time.