Message-ID: <4FB6BA5F.6060906@cornell.edu>
Date: Fri, 18 May 2012 17:08:47 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: cygwin <cygwin@cygwin.com>
Subject: Interpreting a gdb backtrace
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

I'm trying to debug an emacs crash and am having trouble getting a 
useful backtrace after the crash.  Here's an example:

#0  0x00289c08 in ?? ()
No symbol table info available.
#1  0x007ba148 in _malloc_mutex ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.

Aside from the lack of information, the most salient feature of this is 
that _malloc_mutex is actually a variable, not a function, so the 
information for frame #1 makes no sense.

I'm not very experienced at debugging, but I'm wondering if I can get 
anything out of this sort of backtrace.  Or does it just indicate that 
the stack got corrupted?

Thanks in advance for any suggestions.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple