X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <1de001c3c02c$29453000$0600000a@broadpark.no>
From: "Gisle Vanem" <giva AT bgnett DOT no>
To: "djgpp" <djgpp AT delorie DOT com>
Subject: SIGINT under Windows
Date: Thu, 11 Dec 2003 22:17:19 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Reply-To: djgpp AT delorie DOT com

Is there any cure for the unreliable SIGINT generation under Windows 
(especially under Win-XP's ntvdm)?

AFAICS delivery of SIGINT when pressing ^Break is much more reliable 
than pressing ^C (which terminates a program immediately in most
cases).

I tried doing setcbrk(0) after a 'signal(SIGINT,my_handler)'. That seems 
to work reliably, but rearming the SIGINT handler after that, seems to 
make SIGINT unreliable yet again (program abruptly terminated by 
ntvdm it seems).

Since djgpp does SIGINT generation by directly hooking the keyboard
(isn't that still true?), I don't understand how reinstalling the SIGINT should 
have any effect on the internal ntvdm break checking once it's turned
off.

--gv