On Mon, Sep 12, 2011 at 8:04 AM, Florian Berger
<fberger@xxxxxxxxxxxxxxxxx> wrote:
Hi René,
> If you could get the gdb stack trace, that might be helpful too.
Hope that is it:
Python 2.6:
...
(gdb) where
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb74cfdf0 in raise () from /lib/libc.so.6
#2 0xb74d1628 in abort () from /lib/libc.so.6
#3 0xb750c355 in ?? () from /lib/libc.so.6
#4 0x0000000e in ?? ()
#5 0xbf98a9c0 in ?? ()
#6 0x00000400 in ?? ()
#7 0x00000000 in ?? ()
Python 3.2:
...
(gdb) where
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb7515df0 in raise () from /lib/libc.so.6
#2 0xb7517628 in abort () from /lib/libc.so.6
#3 0xb7552355 in ?? () from /lib/libc.so.6
#4 0x0000000d in ?? ()
#5 0xbfd03bb0 in ?? ()
#6 0x00000400 in ?? ()
#7 0x00000000 in ?? ()
I have no experience in gdb debugging, so I hope that is of some use...