Date:	Tue, 12 Oct 1999 12:18:50 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	pavenis AT lanet DOT lv
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Debugging programs with SIGALRM
In-Reply-To:	<B0000104814@stargate.astr.lu.lv>
Message-ID:	<Pine.SUN.3.91.991012121224.8400C-100000@is>
MIME-Version:	1.0
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

On Tue, 12 Oct 1999 pavenis AT lanet DOT lv wrote:

> Another possible way to run into trouble with dbgcom.c:
> 	redefine in debugee key that is translated to SIGINT and try to
> 	use it.

I thought about this before.  I'm not sure it will make any trouble (but 
I will try it later).

But I agree that we should try all those cases and attempt to fix any of
them which can be reasonably fixed, now that the basic machinery is in
place for supporting these weird situations.  I found this SIGALRM 
problem (and also the problems with emulation, see my other mail today) 
because I deliberately tried them.

- Raw text -