Message-Id:	<199905200842.KAA10815@cerbere.u-strasbg.fr>
X-Sender:	muller AT ics DOT u-strasbg DOT fr
X-Mailer:	QUALCOMM Windows Eudora Pro Version 4.0.1
Date:	Thu, 20 May 1999 10:32:02 +0200
To:	djgpp-workers AT delorie DOT com
From:	Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
Subject:	Re: gdb 4.18 for DJGPP (alpha)
References:	<m10k6Zw-0006NpC AT galjas DOT cs DOT vu DOT nl>
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

>Does this ring a bell for someone?  Is it at all reasonable to expect GDB 
>be debugged by itself in a stable manner?  Does v2.02 include known bugs 
>in libdbg.a that could produce such problems?

  I wrote the changes needed in dbgcom.c to get GDB-4.16
be able to debug itself (which I needed for a FPC port of GDB !)

And finally I got something that worked quite well 
But someone made small change to the dbgcom.c code that
I still don't understand :
especially, I did a redirect of the main signals each time 
the child was allowed to continue in hook_dpmi
but this was placed in the global part of  edi_init
and the dbgsig is not restored after !
This might be a problem here !

- Raw text -