This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: help: dumper 1.10 not giving expected stack trace in gdb


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@sourceware.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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]