From: Steve Murphy Date: Tue, 31 Jul 2007 19:19:35 +0000 (+0000) Subject: This probably isn't super-general, but it's a first stab at using kill -11 to generat... X-Git-Tag: 1.2.24~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=330090142ff9f36691a51df1329d09fdc1aad603;p=thirdparty%2Fasterisk.git This probably isn't super-general, but it's a first stab at using kill -11 to generate a core file instead of gcore. git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.2@77842 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/contrib/scripts/ast_grab_core b/contrib/scripts/ast_grab_core index 8f405ebddf..4de519c7f8 100644 --- a/contrib/scripts/ast_grab_core +++ b/contrib/scripts/ast_grab_core @@ -3,8 +3,19 @@ # lame quickie script to snarf a core of a hung asterisk process. # bugs to ast_grab_core, blinky-lights.org (derrick daugherty) +# we have found that gcore doesn't yield as useful a core file +# as that yielded by a signal-caused core dump. So we are going to change +# the strategy to sending a SEGV signal to the asterisk process, +# and have it 'burn to the ground', leaving behind a core file. +# the main difference is that you cannot control where the +# core file will end up. We will assume that safe_asterisk was +# used to start asterisk, and the core file should therefore end +# up in /tmp (because safe_asterisk cd's there before starting asterisk). +# if this is not the case, set DUMPDIR to the place where the core +# file can be found. + DATE=`date +%Y%m%d%H%M` -DUMPDIR=/var/tmp +DUMPDIR=/tmp HOSTNAME=`hostname` ADMINEMAIL="root@localhost" @@ -27,20 +38,16 @@ echo \*\*\* WARNING \*\*\* If the system is not already locked this will cause echo \*\*\* WARNING \*\*\* process to STOP while memory is dumped to disk. echo -/usr/bin/gdb > /dev/null << EOF - attach ${PID} - gcore ${DUMPDIR}/asterisk_${DATE}.core.${PID} - detach - quit -EOF +/usr/bin/kill -11 ${PID} -echo Snarfed! ${DUMPDIR}/asterisk_${DATE}.core.${PID} +echo Snarfed! ${DUMPDIR}/core.${PID} echo echo Trying for a backtrace of the captured core. -/usr/bin/gdb /usr/sbin/asterisk ${DUMPDIR}/asterisk_${DATE}.core.${PID} > /tmp/gdb_dump.${PID} 2> /dev/null << EOF +/usr/bin/gdb /usr/sbin/asterisk ${DUMPDIR}/core.${PID} > /tmp/gdb_dump.${PID} 2> /dev/null << EOF set prompt \n +set print pretty\n echo --------------------------------------------------------------------------------\n echo INFO THREAD info thread @@ -56,7 +63,7 @@ echo Done trying for a bt. echo Notifying admins of the core. -/usr/bin/mail -s "${HOSTNAME} core dumped at ${DUMPDIR}/asterisk_${DATE}.core.${PID}" ${ADMINEMAIL} < /tmp/gdb_dump.${PID} +/usr/bin/mail -s "${HOSTNAME} core dumped at ${DUMPDIR}/core.${PID}" ${ADMINEMAIL} < /tmp/gdb_dump.${PID} /bin/rm /tmp/gdb_dump.${PID} echo Done. echo