Date: Wed, 14 Jan 1998 16:59:46 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Paul Derbyshire <ao950 AT FreeNet DOT Carleton DOT CA>
Cc: djgpp AT delorie DOT com
Subject: Re: Writing a SIGINT handler.
In-Reply-To: <69i519$8c4@freenet-news.carleton.ca>
Message-Id: <Pine.SUN.3.91.980114165806.9833C-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk
Precedence: bulk


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.