Bug#421191: python-gtk2: debug version of gtk library causes Segmentation Fault

[Achim Gaedke]

Hi Loïc!

Why do I do all this? Well, I'd like to have debugging symbols in
libgtk2 and the debugging flags available.

This is what I am hunting:
> The program 'DAMARIS' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadLength (poly request too large or internal Xlib
> length erro'.
>   (Details: serial 4650870 error_code 16 request_code 114 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 DAMARIS uses matplotlib, glade, pygtk and threading.
Sometimes it dies away. I'd like to trace down this error (maybe to
matplotlib).

While skiming throug the source code I found pygtk handing down the
argument lists and tried to run libgtk2-dbg with pygtk.

Could you tell me how to do that? Is it necessary to build pygtk linked
against libgtk2-dgb?
I was not able to find proper instructions to use libgtk2-dbg.

Thanks for an answer, Achim

Loïc Minier wrote:
> On Fri, Apr 27, 2007, Achim Gaedke wrote:
>   
>> add the symbolic links in /usr/lib/debug/usr/lib
>>     
>
>  Why are you adding these links?
>
>