Date: Wed, 14 Jan 1998 20:31:38 -0800 (PST)
Message-Id: <199801150431.UAA16356@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
        Paul Derbyshire <ao950 AT FreeNet DOT Carleton DOT CA>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Writing a SIGINT handler.
Cc: djgpp AT delorie DOT com
Precedence: bulk

At 04:59  1/14/1998 +0200, Eli Zaretskii wrote:
>
>On 14 Jan 1998, Paul Derbyshire wrote:
>
>> Does a SIGINT handler fall under memory locking? (I.e. must it, and
>> anything it touches or calls, be locked?)
>
>No.  SIGINT is not a true exception, it is faked by the DJGPP keyboard 
>handler when it sees either Ctrl-C or Ctrl-BREAK.  By the time your 
>handler is called, you are in a safe state, so you can do anything and 
>don't need to lock.
This is true of all signals, right?  Including hardware-generated ones like
SIGSEGV?

Nate Eldredge
eldredge AT ap DOT net