From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29777-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 29220 invoked by alias); 30 Sep 2007 07:13:07 -0000
Received: (qmail 29198 invoked by uid 22791); 30 Sep 2007 07:13:06 -0000
X-Spam-Check-By: sourceware.org
Received: from romy.inter.net.il (HELO romy.inter.net.il) (213.8.233.24)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 30 Sep 2007 07:13:03 +0000
Received: from HOME-C4E4A596F7 (IGLD-80-230-11-149.inter.net.il [80.230.11.149]) 	by romy.inter.net.il (MOS 3.7.3-GA) 	with ESMTP id IZS19035 (AUTH halo1); 	Sun, 30 Sep 2007 09:12:48 +0200 (IST)
Date: Sun, 30 Sep 2007 18:13:00 -0000
Message-Id: <uk5q8bp8j.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Gordon Prieur <Gordon.Prieur@Sun.COM>
CC: gdb@sourceware.org
In-reply-to: <46FEC75E.9010207@Sun.COM> (message from Gordon Prieur on Sat, 29 	Sep 2007 14:45:02 -0700)
Subject: Re: Strange stack trace on Windows
Reply-to: Eli Zaretskii <eliz@gnu.org>
References:  <46FEC75E.9010207@Sun.COM>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-09/txt/msg00280.txt.bz2

> Date: Sat, 29 Sep 2007 14:45:02 -0700
> From: Gordon Prieur <Gordon.Prieur@Sun.COM>
> 
>     When I interrupt the debugee on Windows I almost never get a stack trace
> with he debuggee information in it. I get similar traces with both MinGW and
> Cygwin gdb commands:
> 
> > 115where
> > 115&"where\n"
> > 115~"#0  0x7c90eb94 in ntdll!LdrAccessResource ()\n"
> > 115~"   from C:\\WINDOWS\\system32\\ntdll.dll\n"
> > 115~"#1  0x7c90e3ed in ntdll!ZwRequestWaitReplyPort ()\n"
> > 115~"   from C:\\WINDOWS\\system32\\ntdll.dll\n"
> > 115~"#2  0x7c9132f8 in ntdll!CsrProbeForWrite () from 
> > C:\\WINDOWS\\system32\\ntdll.dll\n"
> > 115~"#3  0x00003fec in ?? ()\n"
> > 115~"#4  0x0022fa70 in ?? ()\n"
> > 115~"#5  0x0022fa70 in ?? ()\n"
> > 115~"#6  0x00000000 in ?? ()\n"
> > 115^done

If you type "step" repeatedly, do you eventually get to a frame that
is in your program?  If you do, you can get a valid stack trace at
that point.