[Asterisk-Dev] advance debugging?

david.j as davidj.as at gmail.com
Fri Sep 2 01:25:15 MST 2005


Hello I think I've found two non-deadlock bugs in CVS HEAD Asterisk, one in 
SIP with NAT and one interoperability problem in SIP RFC2833 DTMF. I believe 
I have them isolated fairly well and can duplicate them with other 
hardware/environments. I want to post some data on this, but first wanted to 
ask everyone for some input on advance asterisk debugging.

So far I have :
1. A tcpdump, rtp debug, and sip debug and can highlight the problem 
packets.
2. gdb output for "info thread "
"thread apply all bt" ( RTP type bugs to fast for this??)
3. Makefile modified for: 

DEBUG_THREADS = -DDUMP_SCHEDULER -DDEBUG_SCHEDULER -DDEBUG_THREADS 
-DDO_CRASH -DDETECT_DEADLOCKS

OPTIMIZE=+-O6 (yeah its really -O6 ) turned off, DEBUG with -g -pg , 
TRACE_FRAMES = -DTRACE_FRAMES
Note: From my experience -O6 can cause bugs.

4. 'gcore' command, strace
5. oprofile? Not sure how to use it

anything else I am missing? valgrind? Is there a way I can dump all data 
structures in gdb for example, the current state of chan_sip.so? Short of a 
bunch of printf-like statements I think this is the only way I can pin point 
the bug. Can anyone hint me on how to effectively use oprofile to do this?

Thanks,
D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20050902/ca3d5992/attachment.htm


More information about the asterisk-dev mailing list