Comment 13 for bug 286544

Can't backtrace a mono-app with GDB, and mono --debug gives similar error as already stated above:

switchbl8@rrs01:~$ mono --debug /usr/lib/f-spot/f-spot.exe
[Info 13:09:20.131] Initializing DBus
[Info 13:09:20.463] Initializing Mono.Addins
[Info 13:09:20.995] Starting new FSpot server
The program 'f-spot' 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 331 error_code 1 request_code 157 minor_code 19)
  (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.)

or

switchbl8@rrs01:~$ mono --debug /usr/lib/f-spot/f-spot.exe --debug
[Info 13:10:52.522] Initializing DBus
[Debug 13:10:52.855] DBusInitialization took 0.304061s
[Info 13:10:52.855] Initializing Mono.Addins
[Debug 13:10:53.381] Mono.Addins Initialization took 0.525691s
[Info 13:10:53.398] Starting new FSpot server
[Debug 13:10:53.622] Db Initialization took 0.120978s
[Debug 13:10:54.245] QueryToTemp took 0.288803s : SELECT id, time, uri, description, roll_id, default_version_id, rating, md5_sum FROM photos WHERE id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC
[Debug 13:10:54.437] Query took 0.026026s : SELECT * FROM photoquery_temp_0 LIMIT 100 OFFSET 0
The program 'f-spot' 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 331 error_code 1 request_code 157 minor_code 19)
  (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.)

So, please tell me how to create a backtrace, and I will do so.