Date:	Wed, 24 Mar 1999 19:22:01 -0500
Message-Id:	<199903250022.TAA32085@mescaline.gnu.org>
From:	Eli Zaretskii <eliz AT gnu DOT org>
To:	pavenis AT lanet DOT lv
CC:	robert DOT hoehne AT gmx DOT net, djgpp-workers AT delorie DOT com
In-reply-to:	<B0000080872@stargate.astr.lu.lv> (pavenis@lanet.lv)
Subject:	Re: Debugging support in DJGPP
References:	<B0000080709 AT stargate DOT astr DOT lu DOT lv> (pavenis AT lanet DOT lv) <B0000080872 AT stargate DOT astr DOT lu DOT lv>
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

   From: "Andris Pavenis" <pavenis AT lanet DOT lv>

   There are still some relatively small problems with exceptions. 
   But anyway I think they are not so serious. I think that new available
   features are more significant.

In that case, I think we can include this version in v2.03.  DJ?

   Maybe it would be time to change to gdb-4.17 finally. Of course one can build
   gdb-4.16 once more. Is somebody going to build official binaries (or we 
   are waiting for gdb-4.18 ...)?

I don't think we should.  Actually, I just got some inside hint from
one of the Cygnus guys that 4.18 will be a mess when it come sout, due
to some problems which I'm not going to go into.

   So it's not a new problem. It would be nice to fix it of course but as I said
   before I don't know why it happens. It seems to be a bug somwhere in
   libc.a. 

I know about this problem for a long time, but since you said that it
was aregression from the old version, I thought I was mistaken
somehow.

It seems this is not an issue, though, and that v2.03 could have the
new dbgcom.  Thanks for testing it.

- Raw text -