Date: Tue, 10 Dec 2002 07:49:57 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: Andrew Cottrell <acottrel AT ihug DOT com DOT au>,
   DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: DJGPP 2.04 problem list
In-Reply-To: <3DF4D6A7.B712A5F6@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1021210074743.16020A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 9 Dec 2002, Richard Dawe wrote:

> Nope, it's still broken. I tested with gcc 3.2.1, gdb 5.2.1 and one of my
> DJGPP development trees. I got the following, when I tried to debug a program
> built against the libc tree with DWARF-2 debug info:
> 
> "Dwarf Error: bad offset (0x15e

Let me be sure I understand this correctly: are you saying that _any_ 
program produced by GCC 3.2.1 with -gdwarf-2 cannot be debugged by GDB?
Or does the problem happen only with C++ programs, or only with the CVS 
libc, or under some other special circumstances?