From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-18760-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 420 invoked by alias); 22 Jul 2004 19:12:38 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 410 invoked from network); 22 Jul 2004 19:12:37 -0000
Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23)
  by sourceware.org with SMTP; 22 Jul 2004 19:12:37 -0000
Received: from zaretski ([80.230.148.60])
	by aragorn.inter.net.il (MOS 3.4.6-GR)
	with ESMTP id DWN98584;
	Thu, 22 Jul 2004 22:12:22 +0300 (IDT)
Date: Thu, 22 Jul 2004 19:26:00 -0000
From: "Eli Zaretskii" <eliz@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Message-Id: <2914-Thu22Jul2004221106+0300-eliz@gnu.org>
CC: mec.gnu@mindspring.com, kettenis@chello.nl, cagney@gnu.org,
        gdb@sources.redhat.com
In-reply-to: <20040722151701.GA20596@gnat.com> (message from Joel Brobecker on
	Thu, 22 Jul 2004 08:17:01 -0700)
Subject: Re: [6.2] PROBLEMS file
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <20040722093553.624FF4B104@berman.michael-chastain.com> <20040722151701.GA20596@gnat.com>
X-SW-Source: 2004-07/txt/msg00285.txt.bz2

> Date: Thu, 22 Jul 2004 08:17:01 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> 
> We saw the same sort of issues on Windows as well, trying to unwind
> from functions in the ntdll DLL. Unfortunately in that case, we don't
> get an infinite backtrace, we get a backtrace that doesn't provide
> the part that the user is probably looking for (the part refering to
> his code, before the call to the ntdll services). Something like this:
> 
>     #0  0x7ffe0304 in ?? ()
>     #1  0x77f7f4af in ntdll!ZwWaitForSingleObject () from ntdll.dll
>     #2  0x77e7788b in WaitForSingleObjectEx () from /WINDOWS/system32/KERNEL32.DLL
>     #3  0x00000778 in ?? ()
>     #4  0x00000000 in ?? () from 
>     #5  0x010df2c8 in ?? ()
>     #6  0x000003e8 in ?? ()
>     [snip]
>     #27 0x77e79d6a in WaitForSingleObject () from /WINDOWS/system32/KERNEL32.DLL
>     #28 0x00000778 in ?? ()
>     #29 0x000003e8 in ?? ()
>     #30 0x00000000 in ?? () from 
>     #31 0x61074971 in siginterrupt () from /bin/cygwin1.dll
>     Previous frame inner to this frame (corrupt stack?)
> 
> In the backtrace above, only frame 0 to 2 are correct. After that,
> GDB goes in limbo until it finally finds out that something is wrong.

That is exactly what I saw with the DJGPP port.  Was the program in
your case compiled with DWARF2 debug info or with some other format?