Date:	Tue, 11 Jun 2002 08:51:11 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	sandmann AT clio DOT rice DOT edu
cc:	acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com
Subject:	Re: unixy sbrk and win2k
In-Reply-To:	<10206110513.AA18793@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.1020611084657.2609O-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 11 Jun 2002 sandmann AT clio DOT rice DOT edu wrote:

> Thus, to test this patch we would need someone to do an emacs rebuild with
> updated crt0.o and see if it behaves better on Win2K.

Yes.

> In particular, if
> emacs fields any hardware interrupts and does anything interesting with
> them, I wonder if they still fire.  SIGINT?

Emacs doesn't hook any hardware interrupts (apart of those hooked by the 
DJGPP standard startup code).

If someone wants to shake Emacs with interrupts, pressing Ctrl-BREAK at 
various places, perhaps several times in quick succession, would be the 
first idea I'd try.  (SIGINT produced by Ctrl-C is disabled in Emacs, 
since Ctrl-C is used in many Emacs key sequences.)

Another idea would be to evaluate a Lisp expression that causes SIGFPE, 
and see what that does on NT/W2K/XP.  I'd expect some nasty surprises 
there as well.

- Raw text -