X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,KHOP_THREADED,SPF_NEUTRAL,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4FB6E993.2010601@cornell.edu>
Date: Fri, 18 May 2012 20:30:11 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Interpreting a gdb backtrace
References: <4FB6BA5F DOT 6060906 AT cornell DOT edu> <jp6jdu$o7l$1 AT dough DOT gmane DOT org>
In-Reply-To: <jp6jdu$o7l$1@dough.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-CORNELL-SPAM-CHECKED: Pawpaw
X-Original-Sender: kbrown AT cornell DOT edu - Fri May 18 20:30:22 2012
X-PMX-CORNELL-REASON: CU_White_List_Override
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 5/18/2012 6:45 PM, jojelino wrote:
> On 2012-05-19 AM 6:08, Ken Brown wrote:
>> 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.
>>
> i think you should provide symbol file of emacs to gdb. if it was
> stripped, you had better to build emacs from source code with -g (at
> least gcc 4.5 for CFI that gdb need to backtrace the stack frame with
> ease).

I built emacs with -g -O0.  gdb had the symbol table at the start of the 
debugging session.  It's just after the crash that everything is messed up.

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