X-Sent:	15 Jul 2001 15:57:43 GMT
Message-ID:	<000a01c10d47$14145340$e33e1d18@nycap.rr.com>
From:	"Matthew Conte" <matt AT conte DOT com>
To:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc:	<djgpp AT delorie DOT com>
References:	<001d01c10d33$d7e6b9c0$e33e1d18 AT nycap DOT rr DOT com> <3405-Sun15Jul2001183438+0300-eliz AT is DOT elta DOT co DOT il>
Subject:	Re: '9x and raise in interrupt service routines
Date:	Sun, 15 Jul 2001 11:59:05 -0400
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2479.0006
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2479.0006
Reply-To:	djgpp AT delorie DOT com

From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

[...]
> Moreover, the default SIGINT handler tries to unwind the stack,
which
> is one-way ticket to disaster when the stack isn't yours.  And there
> are other possible complications, depending on what your code does,
> exactly.

i would guess that raise is attempting to unwind the stack; it's easy
to see why this would cause the chain of execution to go off into the
weeds.

> In other words: don't do that!

ok!  =]

> Why don't you simply chain to the previous keyboard handler?  That
> would do what you want, and do it safely, because the previous
handler
> is the one installed by the startup code, which generates SIGINT in
> any normal DJGPP application.

yes, that does work.  unfortunately, all keypresses get passed through
to the default handler, and i get that annoying "keyboard buffer
overflow" noise out of the pc-speaker.  any way to disable this, yet
still allow CTRL-C/CTRL-BREAK to pass through?

thanks for the help,
matthew.

- Raw text -