From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Wed, 26 Jun 2002 13:34:21 +0300
MIME-Version: 1.0
Subject: Re: gcc-3.1.X and DWARF2 debugging info for DJGPP
Message-ID: <3D19C2DD.1004.8F32B0@localhost>
References: <3D19AC42 DOT 32660 DOT 36E3DB AT localhost>
In-reply-to: <Pine.SUN.3.91.1020626130755.12266A-100000@is>
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Reply-To: djgpp-workers AT delorie DOT com

On 26 Jun 2002 at 13:08, Eli Zaretskii wrote:

> 
> On Wed, 26 Jun 2002 pavenis AT lanet DOT lv wrote:
> 
> > Problem: gdb-5.2 is needed. gdb-5.1 will not work OK with DWARF2 debugging 
> > info generated by dgb-5.1. What are Your plans with GDB-5.2?
                                         ^^^^^^  mistake, I thought gcc-3.1
> 
> I will make a port when I have time.  Hopefully, soon.

I have my own binary package, but it's not prepared for uploading (no DSM's
etc.). I already got a similar remarks about package of binutils-2.12.1 I built
soon after that was released.

Also one should rebuild also bfdstubify with newer libbfd to be useable with
DWARF2 debug info.

> > Advantages: warning messages about exceeding 64K source lines are gone now at 
> > build time, so complete debugging info is available now.
> 
> You mean, with -gcoff?

Of course it cannot be done with -gcoff.  I thought the default -g. One can 
still use -gcoff of course.

Also change to DWARF2 debugging info as the default would force to 
put bfdsymify instead of symify. Maybe it's worth to release it in a separate
package (not as a part of gdbXXXb.zip)

Andris