From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29769-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 6374 invoked by alias); 29 Sep 2007 21:44:48 -0000
Received: (qmail 6366 invoked by uid 22791); 29 Sep 2007 21:44:48 -0000
X-Spam-Check-By: sourceware.org
Received: from sca-es-mail-2.Sun.COM (HELO sca-es-mail-2.sun.com) (192.18.43.133)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 29 Sep 2007 21:44:45 +0000
Received: from fe-sfbay-09.sun.com ([192.18.43.129]) 	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l8TLihZv006656 	for <gdb@sourceware.org>; Sat, 29 Sep 2007 14:44:43 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com  (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))  id <0JP500J01G42Q900@fe-sfbay-09.sun.com>  (original mail from Gordon.Prieur@Sun.COM) for gdb@sourceware.org; Sat,  29 Sep 2007 14:44:43 -0700 (PDT)
Received: from [192.168.1.67] ([69.107.61.254])  by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb  28 2007)) with ESMTPSA id <0JP500MUSGEJH480@fe-sfbay-09.sun.com> for  gdb@sourceware.org; Sat, 29 Sep 2007 14:44:43 -0700 (PDT)
Date: Sat, 29 Sep 2007 22:01:00 -0000
From: Gordon Prieur <Gordon.Prieur@Sun.COM>
Subject: Strange stack trace on Windows
To: gdb@sourceware.org
Message-id: <46FEC75E.9010207@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.13 (Windows/20070809)
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/msg00272.txt.bz2

Hi,

    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

    Its not that I'm looking at the wrong thread, I've checked all threads
(and set the current thread to the user thread). Can anybody explain 
this and
tell me how to get to user data?

Thanks,
Gordon