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
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,
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
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 ?
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
5 matches
Mail list logo