Date:	Thu, 2 Jan 2003 07:35:38 +0000 (GMT)
From:	andris AT hal DOT astr DOT lu DOT lv
X-X-Sender:	andris AT laser4 DOT metsahovi DOT fgi DOT fi
To:	djgpp AT delorie DOT com
Subject:	Re: ANNOUNCE: DJGPP packages of gdb 5.3
In-Reply-To:	<200212291526.gBTFQJU25879@delorie.com>
Message-ID:	<Pine.LNX.4.50.0301020721510.18498-100000@laser4.metsahovi.fgi.fi>
References:	<200212291526 DOT gBTFQJU25879 AT delorie DOT com>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 29 Dec 2002, Richard Dawe wrote:

> Hello.
>
> I'd like to announce DJGPP packages of gdb 5.3.
>
> The major change in gdb 5.3 for DJGPP users is that GDB now supports C/C++
> preprocessor macros - it can expand macros. For more details, see
> gnu/gdb-5.3/gdb/NEWS, once a package of gdb 5.3 has been installed, or read
> the announcement on the web here:
>

Only one note.

I had to modify one of the files in gdb subdirectory to
workaround one GDB internal error while reading debugging information
about preprocessor macros in some cases due to (perhaps) one bug in GCC
which appears only when preprocessor options -imacros and similar are
being used. I reproduced this problem also under Linux:

When -imacros is used (for DJGPP it is used to get sys/version.h included
automatically at start) #include statement from the first line of source
file is somewhere misreported as being from line 2 and that causes GDB
crying about internal error.

I didn't have enough time to try to dig into more details and to find
where something is wrong in debug info. I only modify GDB not to generate
internal error in this case. Of course it's ugly, but I don't think that
there is another way before GCC is fixed.

Unfortunatelly I don't have a workaround patch here around me now. So I
can send it only after I return to Finland next week (I'm currently in
Latvia for Christmass and New Year holydays)

Andris

- Raw text -