/path/to/src/asterisk/doc/README.backtrace
Kohler, Jeffrey wrote:
I was able to eventually figure it out. For anyone as linux unsavvy as
myself:
- # gdb /usr/sbin/asterisk /tmp/core.21713
- # bt
Sorry for the stupid question
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kohler,
Jeffrey
Sent: Friday, July 21, 2006 8:21 AM
To: Asterisk Developers Mailing List
Subject: [asterisk-dev] Asterisk Core Dumps
I've been experiencing some Asterisk crashes and was trying to look at
the core dumps to figure out what is going wrong. Unfortunately I'm not
really even sure where to start. (I'm a Windows developer by trade so
please excuse my ignorance)
Here's what I've done so far:
- run Asterisk with the safe_asterisk script
- when Asterisk crashed it produced a dump file - core.21713
- From a command line, I ran gdb
- # core-file /tmp/core.21713
- # bt
-
I did get a stack trace, however, it simply lists a series of addresses.
How can I get symbolic information to make sense of this?
Is there a better method of examining core files?
--
Now accepting new clients in Birmingham, Atlanta, Huntsville,
Chattanooga, and Montgomery.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
