From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10907 invoked by alias); 1 Oct 2007 14:03:26 -0000 Received: (qmail 10898 invoked by uid 22791); 1 Oct 2007 14:03:25 -0000 X-Spam-Check-By: sourceware.org Received: from sca-es-mail-1.Sun.COM (HELO sca-es-mail-1.sun.com) (192.18.43.132) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 01 Oct 2007 14:03:16 +0000 Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l91E3EDd026093 for ; Mon, 1 Oct 2007 07:03:15 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JP800C01K8TZK00@fe-sfbay-10.sun.com> (original mail from Gordon.Prieur@Sun.COM) for gdb@sourceware.org; Mon, 01 Oct 2007 07:03:14 -0700 (PDT) Received: from [129.146.82.55] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JP8000A9KDB9O60@fe-sfbay-10.sun.com>; Mon, 01 Oct 2007 07:03:11 -0700 (PDT) Date: Mon, 01 Oct 2007 14:03:00 -0000 From: Gordon Prieur Subject: Re: Strange stack trace on Windows In-reply-to: To: Eli Zaretskii Cc: gdb@sourceware.org Message-id: <4700FE1E.6040201@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <46FEC75E.9010207@Sun.COM> User-Agent: Thunderbird 1.5 (X11/20060113) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00005.txt.bz2 Eli Zaretskii wrote: >> Date: Sat, 29 Sep 2007 14:45:02 -0700 >> From: Gordon Prieur >> >> 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. > Sometime yes, sometimes no. I implemented that solution abotu 6 months ago but backed it out because it was just as likely to crash gdb:-( or hang my IDE (netbeans). Gordon