Bug#375967: Acknowledgement (Segfaults)

2006-06-29 Thread Anton Ivanov
I tried to run it under gdb without success. It gets a signal 33 after a while which I think is actually a GDB artefact. Any ideas on how to debug this will be appreciated. -- Understanding is a three-edged sword: your side, their side, and the truth. --Kosh Naranek A. R. Ivanov

Bug#375967: Acknowledgement (Segfaults)

2006-06-29 Thread Thomas Girard
Selon Anton Ivanov [EMAIL PROTECTED]: I tried to run it under gdb without success. It gets a signal 33 after a while which I think is actually a GDB artefact. Any ideas on how to debug this will be appreciated. If this is *really* an artefact you can use handle SIG33 noprint nostop. HTH,

Bug#375967: Acknowledgement (Segfaults)

2006-06-29 Thread Anton Ivanov
Thomas Girard wrote: Selon Anton Ivanov [EMAIL PROTECTED]: I tried to run it under gdb without success. It gets a signal 33 after a while which I think is actually a GDB artefact. Any ideas on how to debug this will be appreciated. If this is *really* an artefact you can use handle

Bug#375967: Acknowledgement (Segfaults)

2006-06-29 Thread Thomas Girard
Selon Anton Ivanov [EMAIL PROTECTED]: famd: NetConnection.c++:252: void NetConnection::flush(): Assertion `ret == omsgList-len' failed. Program received signal SIGABRT, Aborted. 0xb7def83b in raise () from /lib/tls/libc.so.6 Great. And what does `bt full' give you then ?

Bug#375967: Acknowledgement (Segfaults)

2006-06-29 Thread Anton Ivanov
Thomas Girard wrote: Selon Anton Ivanov [EMAIL PROTECTED]: famd: NetConnection.c++:252: void NetConnection::flush(): Assertion `ret == omsgList-len' failed. Program received signal SIGABRT, Aborted. 0xb7def83b in raise () from /lib/tls/libc.so.6 Great. And what does `bt full' give