aMule Forum

English => Backtraces => Topic started by: chemical on October 22, 2006, 12:50:07 PM

Title: amuled - Program received signal SIGTRAP, Trace/breakpoint trap.
Post by: chemical on October 22, 2006, 12:50:07 PM

Code: [Select]

2006-10-21 21:15:00: New external connection accepted
2006-10-21 21:15:00: Connecting client: aMulecmd CVS
2006-10-21 21:15:00: Access granted.
2006-10-21 21:15:00: External connection closed.
2006-10-21 21:20:00: New external connection accepted
2006-10-21 21:20:00: Connecting client: aMulecmd CVS
2006-10-21 21:20:00: Access granted.
2006-10-21 21:20:00: External connection closed.
[New Thread 458781 (LWP 14344)]
2006-10-21 21:21:31: Hasher: Starting to create MD4 and AICH hash for file: 004.part
2006-10-21 21:21:46: ThreadScheduler: Completed task 'Hashing - /donkey/amule/temp/004.part', 0 tasks remaining.
2006-10-21 21:21:46: Suspending upload of file:
[Thread 458781 (LWP 14344) exited]

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 196621 (zombie)]
0x00000000 in ?? ()
(gdb) thread apply all bt full

Thread 30 (Thread 458781 (LWP 14344)):
#0  0x40030571 in __linuxthreads_death_event () from /lib/i686/libpthread.so.0
No symbol table info available.
#1  0x45fffe34 in ?? ()
No symbol table info available.
#2  0x401d77a8 in __JCR_LIST__ () from /home/donkey/lib/libwx_baseu-2.7.so.0
No symbol table info available.
#3  0x45fffd64 in ?? ()
No symbol table info available.
#4  0x401745e8 in wxMutex::Unlock () from /home/donkey/lib/libwx_baseu-2.7.so.0
No symbol table info available.
Previous frame inner to this frame (corrupt stack?)
#0  0x00000000 in ?? ()
(gdb)

I guess this is not helpful, but I post it anyway.

Title: Re: amuled - Program received signal SIGTRAP, Trace/breakpoint trap.
Post by: phoenix on October 23, 2006, 03:50:00 PM

chemical,

Code: [Select]

Program received signal SIGTRAP, Trace/breakpoint trap.

SIGTRAP is generated as a response to a breakpoint. This is normal when you are inside the debuger. You should just type 'c' to continue. Check your breakpoints or other conditions that might cause a SIGTRAP.

Cheers!

Title: Re: amuled - Program received signal SIGTRAP, Trace/breakpoint trap.
Post by: chemical on October 23, 2006, 03:57:53 PM

Guess someone of the devs did a TRAP in the source then (20061017)? Did not configure anything like that.

Just running in a gdb to be able to generate useful traces for you.

Thanks anyway

Title: Re: amuled - Program received signal SIGTRAP, Trace/breakpoint trap.
Post by: phoenix on October 23, 2006, 04:01:35 PM

Quote

Guess someone of the devs did a TRAP in the source then (20061017)? Did not configure anything like that.

lol, no, we are not THAT crazy :D

Run it outside the debugger. After the program crashes, you can start dgb like that:

$gdb /path/to/amule /path/to/core

And then use bt or bt full to generate the trace.

Cheers!