Date:	Mon, 27 Jan 1997 11:48:08 +0100 (MET)
From:	Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
Reply-To:	Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	DJ Delorie <dj AT delorie DOT com>, DJGPP workers <djgpp-workers AT delorie DOT com>
Subject:	Re: GDB and static variables
In-Reply-To:	<Pine.SUN.3.91.970126172658.6498J-100000@is>
Message-Id:	<Pine.HPP.3.95q.970127113043.23237G-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version:	1.0

Here now my remarks to that topic.

Adding stabs support to gcc in DJGPP is very easy. (Defining only
some few macros on go32.h). I'm working with this since a long
time without any problems but with many improvements.
But there are some problems which I will mention here and
because of them I didn't want to send a patch to the FSF
(but if you think I should after reading below, I will do it):

The biggest problem is, that you cannot mix stabs and coff
debugging information. In general this is possible but it
prevents you from debugging any file which has both formats.
I tried to find the reason for some days, but I hadn't success.
I have located the misfeature to the corrupted line number
information but couldn't fix it.

The next problem is, which format should be the default for
DJGPP? I'm using for my own stabs as default (selected with -g),
and as Eli asked, there is no problem to select coff debugging
with -gcoff.

To DJ's question, how easy it is to add stabs support to the
stock DJGPP debuggers (edbug and fsdb): Because I don not know
so much about the stabs format (I'm only using it) I cannot
say how hard it is, but if I see the large source files in
GDB which handle the stabs debugging, I think it will be no
easy task.

BTW: My patch fixes also the bug with the '-dumpbase foo.cc' when
compiling foo.cpp.


Robert

- Raw text -