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

[Robert Baruch <autophile at zoominternet dot net>]

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.

Thanks for your help,

--Rob


$ gdb --core=t.exe.core
GNU gdb 2003-09-20-cvs (cygwin-special)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
#0  0x7ffe0304 in ?? ()
(gdb) info threads
 3 process 2056  0x77f5f2f2 in ntdll!KiUserCallbackDispatcher ()
 2 process 2224  0x7ffe0304 in ?? ()
* 1 process 3624  0x7ffe0304 in ?? ()
(gdb) where
#0  0x7ffe0304 in ?? ()
#1  0x77f5c534 in ntdll!ZwWaitForSingleObject ()
#2  0x77e7a62d in WaitForSingleObjectEx ()
#3  0x00000778 in ?? ()
(gdb) thread 2
[Switching to thread 2 (process 2224)]#0  0x7ffe0304 in ?? ()
(gdb) where
#0  0x7ffe0304 in ?? ()
#1  0x77f5c294 in ntdll!ZwSetInformationThread ()
#2  0x77e72689 in SetThreadPriority ()
#3  0x6100fe22 in cygwin_stackdump ()
#4  0xfffffff0 in ?? ()
(gdb) thread 3
[Switching to thread 3 (process 2056)]#0  0x77f5f2f2 in 
ntdll!KiUserCallbackDispatcher ()
(gdb) where
#0  0x77f5f2f2 in ntdll!KiUserCallbackDispatcher ()
(gdb)

Attachment: cygcheck.txt.gz
Description: application/gzip

--
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/