Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 12 Oct 2004 08:28:43 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: setjmp/longjmp & signal handlers bug In-Reply-To: <20041012023830.GF17461@trixie.casa.cgf.cx> Message-ID: References: <20041011235128 DOT GD17461 AT trixie DOT casa DOT cgf DOT cx> <20041012023830 DOT GF17461 AT trixie DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Mon, 11 Oct 2004, Christopher Faylor wrote: > On Mon, Oct 11, 2004 at 08:56:52PM -0500, Brian Ford wrote: > >If the handler is set to a function, then first either the handler is > >reset to SIG_DFL, or an implementation dependent blocking of the signal > >is performed, and next the handler is called... > > > >That's Cygwin's implementation dependent blocking? > > Both cygwin and newer versions of linux, apparently. Ok, this doesn't play well with old style *NIX code, but... > >Can I just unblock it before calling signal again then? > > Yes. Have you tried it? > > Either clear the blocking with sigprocmask or use sigsetjmp and siglongjmp. Yes, this works. Thank you for your time and explanation. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/