Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 31 Dec 2003 01:35:12 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: help: dumper 1.10 not giving expected stack trace in gdb
Message-ID: <20031231063511.GA2113@redhat.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3FF1F041 DOT 9010506 AT zoominternet DOT net> <Pine DOT GSO DOT 4 DOT 56 DOT 0312302135360 DOT 18706 AT slinky DOT cs DOT nyu DOT edu> <3FF2414D DOT 8060507 AT zoominternet DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FF2414D.8060507@zoominternet.net>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

On Tue, Dec 30, 2003 at 10:23:57PM -0500, Robert Baruch wrote:
>Igor Pechtchanski wrote:
>
>>
>>If I'm reading the code correctly, the stackdump file is generated from
>>the failed thread.  The core file contains the information about all
>>threads, with no info on what the current (failed) one is.  So, try
>>running 'info threads' in gdb, and then switch to each thread using
>>'thread N' until you find the one that crashed.
>>	Igor
>>
>Hi Igor,
>
>Thanks for the reply. I checked the trace on all threads, but no thread 
>showed the expected trace (as shown below). Any ideas on how to further 
>solve this problem? I'm also attaching the output of cygcheck -s, in 
>case that holds a clue.

The core dump occurred in a function which does not have a frame pointer.
This screws up stack dumps on x86 systems.  There isn't really much that
you can do about this.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

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