X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Fri, 17 May 2002 14:00:31 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	pavenis AT lanet DOT lv
Message-Id:	<8361-Fri17May2002140030+0300-eliz@is.elta.co.il>
X-Mailer:	emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<3CE4FE5E.25829.48C43F@localhost> (pavenis@lanet.lv)
Subject:	Re: gcc 3.1
References:	<Pine DOT A41 DOT 4 DOT 05 DOT 10205171044150 DOT 16248-100000 AT ieva06> (message from Andris Pavenis on Fri, 17 May 2002 10:51:41 +0300 (WET)) <3CE4FE5E DOT 25829 DOT 48C43F AT localhost>
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

> From: pavenis AT lanet DOT lv
> Date: Fri, 17 May 2002 12:58:06 +0300
>  
> Unlikely. Anyway it's not a fatal problem, as it happens only then when
> one uses DWARF-2 debugging info and already have unresolved 
> references from linker (so nothing is additionally broken, not counting
> already broken user program ... )

Is the fix known?  If so, perhaps it could be applied to the DJGPP
port.  I mean, previous versions of GCC did allow DWARF-2 without any
problems; could we just get back to that?

It is IMHO not good to have a GCC port which effectively disallows
using DWARF-2 debugging.  (Although it's not a fatal problem, given
that COFF and stabs still work.)

> Only we should be prepared for storm of questions about these messages.

Why ``a storm''?  -ggdb is not the default, is it?  Does RHIDE use it
by default, perhaps?  If not, only users who know about DWARF-2 will
bump into this problem.

- Raw text -