John Levon wrote: > You know the drill. Backtrace etc
Unfortunately, I'm unable to get a decent backtrace (some king of gdb bug?) Program received signal SIGABRT, Aborted. [Switching to Thread 1024 (LWP 28839)] 0x407ae0a1 in kill () from /lib/libc.so.6 (gdb) bt #0 0x407ae0a1 in kill () from /lib/libc.so.6 #1 0x407ade99 in raise () from /lib/libc.so.6 #2 0x407af364 in abort () from /lib/libc.so.6 And gdb seems to get stuck on an endless loop. Anyway, it was introduced before 19:15 (i.e _before_ your last big changes) Strange if you don't get it. Can somebody confirm it? Alfredo
