Date:	Mon, 26 Mar 2001 13:30:34 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	pavenis AT lanet DOT lv, Mel Corley <mcorley AT engr DOT latech DOT edu>,
	djgpp-workers AT delorie DOT com
Subject:	Re: gcc2953 and RHIDE debugging
In-Reply-To:	<Pine.SUN.3.91.1010326130917.8356B-100000@is>
Message-ID:	<Pine.SUN.3.91.1010326132923.8356D-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

My message, repeated below, bounced from the RHIDE list (apparently, it 
doesn't let non-subscribers post).  If you think what I say is important, 
please forward to the list.

On Mon, 26 Mar 2001, I wrote:

> On Mon, 26 Mar 2001 pavenis AT lanet DOT lv wrote:
> 
> > For comparisson: my build of gcc-3.0 20010314 development version 
> > (from CVS) for DJGPP seems to have correct line numbers in debug 
> > info with -gcoff.
> 
> Perhaps it would be possible to identify the changes in the
> development sources that bring -gcoff support back, and retrofit them 
> into GCC 2.95.3.  Then we could make an updated release.
> 
> It is IMHO unfortunate that the stable release doesn't support COFF 
> debug info.  I think this makes its value for DJGPP users much less that 
> it could have been.  I also anticipate a flood of FAQs as more people 
> discover this problem.  I think it's worth some effort to try to correct 
> this as quickly as possible.
> 

- Raw text -