Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E22A90E.93F707DE@phekda.freeserve.co.uk>
Date: Mon, 13 Jan 2003 11:54:54 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: Andris Pavenis <pavenis AT latnet DOT lv>
CC: djgpp AT delorie DOT com
Subject: Re: ANNOUNCE: DJGPP packages of gdb 5.3
References: <200212291526 DOT gBTFQJU25879 AT delorie DOT com> <200301071120 DOT 23447 DOT pavenis AT latnet DOT lv> <3E21518F DOT 9F54AC8A AT phekda DOT freeserve DOT co DOT uk> <200301131250 DOT 57037 DOT pavenis AT latnet DOT lv>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

Andris Pavenis wrote:
[snip]
> It's a problem with debug info about preprocessor defines and DWARF2
> debugging info, so it oftem (but not in all cases) occur when -g3
> (-gdwarf2-3) is specified:

I don't think I've seen this failure.

> preprocessor option  -imacros ... (we use it from specs to get sys/version.h
> in) causes GCC-3.X (at least GCC-3.1 qand GCC-3.2.1) missreport in debug
> info include from the 1st line of source file as being from 2nd one. If the
> same symbol is defined in include file really included from line 2 (eg. with
> proper #undefine not to have warnings), then one is getting GDB internal
> error. My patch simply silences GDB, not to complain about that. Even if we
> would now have a fix for GCC, it would be best to add this workaround.
[snip]

Thanks for the explanation. I'll upload the new packages soon.

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]