A Ter, 2004-04-06 �s 19:24, Johan Dahlin escreveu:
> >     Program received signal SIGSEGV, Segmentation fault.
> >     0xdd88f724 in strlen () from /usr/lib/libc.so.1
> >     (gdb) bt
> >     #7  0xdd648ed3 in object_doc_descr_get (self=0x818a3b8, obj=0x0, 
> >         type=0xdd4638a0) at pygtype.c:1010
> 
> obj=0x0 seems to be the problem.

  Keep in mind that, due to gcc optimizations that gdb is not aware of,
NULL parameters often appear in gdb because the slot for this variable
may be reused for another variable.

  Yes, it's ugly, but could be perfectly normal.  The only way to be
sure is to recompile pygtk with CFLAGS="-g -O0".

  Best regards.

-- 
Gustavo Jo�o Alves Marques Carneiro
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
The universe is always one step beyond logic.

_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to