[asterisk-bugs] [Asterisk 0017721]: [patch] suggested documentation update to doc/backtrace.txt

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17721 
====================================================================== 
Reported By:                kshumard
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17721
Category:                   Documentation
Reproducibility:            N/A
Severity:                   text
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0-beta1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-07-26 15:25 CDT
Last Modified:              2010-07-27 12:25 CDT
====================================================================== 
Summary:                    [patch] suggested documentation update to
doc/backtrace.txt
Description: 
I encountered the same issue as 0017704, and before I saw that it had
already been filed I walked through doc/backtrace.txt to refresh my memory
of that process. The attached includes suggested changes to that
documentation file, primarily seeking to match up the doc with actual
behavior.

One of the biggest changes I saw is that the core file is now just called
"core" instead of core.<asterisk pid> and that it apparently gets dumped in
pwd instead of /tmp/ -- or is my system strange?

Standard `gdb -v` output was also updated, and there are a few grammar
fixes.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0017704 [patch] Asterisk 1.8-beta1 crash on &qu...
====================================================================== 

---------------------------------------------------------------------- 
 (0125122) lmadsen (administrator) - 2010-07-27 12:25
 https://issues.asterisk.org/view.php?id=17721#c125122 
---------------------------------------------------------------------- 
-In the event that there are multiple core files present (as in the
-above example), it is important to look at the file timestamps in
-order to determine which one you really intend to look at.
+After Asterisk crashes, a file named "core" will be dumped in the
+present working directory of the Linux shell from which Asterisk
+was started.



Per davidw that line should probably be modified to have a "footer" or
reference like [1] placed next to the word "core" to state that the file
name is dependent upon OS implementation, and that the use of safe_asterisk
will place the core file in /tmp by default (as set by the ${DUMPDROP}
variable in safe_asterisk).

The name of the core file will be renamed as well (per davidw):

                       PID=`cat ${ASTPIDFILE}`
                        DATE=`date "+%Y-%m-%dT%H:%M:%S%z"`
                        if test -f /tmp/core.${PID} ; then
                                mv /tmp/core.${PID}
${DUMPDROP}/core.`hostname`-$DATE &
                        elif test -f /tmp/core ; then
                                mv /tmp/core
${DUMPDROP}/core.`hostname`-$DATE &
                        fi 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-27 12:25 lmadsen        Note Added: 0125122                          
======================================================================