delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2000/12/07/05:45:54

Date: Thu, 7 Dec 2000 12:19:03 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP linker script update
In-Reply-To: <3A2E531B.8670.20FE7F@localhost>
Message-ID: <Pine.SUN.3.91.1001207121839.26453I-100000@is>
MIME-Version: 1.0
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

On Wed, 6 Dec 2000, Mark E. wrote:

> I'll have to rely on someone who knows about gdb internals to please get 
> dwarf2 configured in for DJGPP there once the binutils patch goes in. 

???  Isn't GDB already configured to support dwarf2 (and many other
formats)?  When GDB is built for DJGPP, all the *read.c modules,
including dwarf2read.c, are linked in, IIRC.

Do we need to configure Binutils for dwarf2 as well, when compiling
GDB?

> My current thinking is that we will be able to debug with dwarf2
> when gcc 3.0 is released.

What's the plans for SYMIFY?

> I can't imagine gcc 3.0 being released before a version of gdb 
> with the neccessary changes to support the new abi is released. So I'd say 
> when gcc 3.0 is released, dwarf2 ready versions of binutils and gdb will be 
> out and so we'll be able to use dwarf2.

I hope you are right.  Discussions on the GDB mailing list seem to
indicate that supporting the new ABI is not an easy project, because
the old ABI support cannot be dropped.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019