Date: Mon, 24 May 1999 11:48:37 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
cc: djgpp-workers AT delorie DOT com
Subject: Re: gdb 4.18 for DJGPP (alpha)
In-Reply-To: <199905200842.KAA10815@cerbere.u-strasbg.fr>
Message-ID: <Pine.SUN.3.91.990524114348.14456D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Thu, 20 May 1999, Pierre Muller wrote:

> 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 !

Could you please elaborate on the nature of the possible problems, and 
tell exactly what change are you talking about?

Btw, I find much of the code added to dbgcom.c under-documented to a 
disturbing degree.  It would be nice to add a few more comments there 
about what's going on, and why, including pointers to specific problems 
solved by the various tricks.  I'm afraid we would otherwise have code 
that cannot be maintained without breaking.

No offence meant to those who labored on that code, of course.