[asterisk-commits] jpeeler: trunk r121805 - in /trunk: ./ doc/backtrace.txt

[SVN commits to the Asterisk project]

Author: jpeeler
Date: Wed Jun 11 11:11:40 2008
New Revision: 121805

URL: http://svn.digium.com/view/asterisk?view=rev&rev=121805
Log:
Merged revisions 121804 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r121804 | jpeeler | 2008-06-11 11:11:09 -0500 (Wed, 11 Jun 2008) | 1 line

add instructions for logging gdb output via set logging on
........

Modified:
    trunk/   (props changed)
    trunk/doc/backtrace.txt

Propchange: trunk/
------------------------------------------------------------------------------
Binary property 'branch-1.4-merged' - no diff available.

Modified: trunk/doc/backtrace.txt
URL: http://svn.digium.com/view/asterisk/trunk/doc/backtrace.txt?view=diff&rev=121805&r1=121804&r2=121805
==============================================================================
--- trunk/doc/backtrace.txt (original)
+++ trunk/doc/backtrace.txt Wed Jun 11 11:11:40 2008
@@ -75,6 +75,11 @@
 Loaded symbols for /usr/lib/asterisk/modules/app_externalivr.so
 #0  0x29b45d7e in ?? ()
 (gdb)
+
+In order to make extracting the gdb output easier, you may wish to
+turn on logging using "set logging on". This command will save all
+output to the default file of gdb.txt, which in the end can be 
+uploaded as an attachment to the bug tracker.
 
 Now at the gdb prompt, type: bt
 You would see output similar to:
@@ -178,8 +183,9 @@
 
 That output tells us crucial information about each thread.
 
-Now, just create an output.txt file and dump your "bt full"
-(and/or "bt") ALONG WITH "thread apply all bt" into it.
+Now, if you turned on logging upload your gdb.txt file. Otherwise,
+create an output.txt file and dump your "bt full" (and/or "bt")
+ALONG WITH "thread apply all bt" into it.
 
 Note: Please ATTACH your output, DO NOT paste it as a note.