delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Date: | Fri, 15 Feb 2008 10:45:47 +0100 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: signals of type SIGSEGV handled only once (in multithreaded process) |
Message-ID: | <20080215094547.GU25954@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <20080215083751 DOT 535E978014 AT ems008 DOT s DOT etech DOT sk> |
MIME-Version: | 1.0 |
In-Reply-To: | <20080215083751.535E978014@ems008.s.etech.sk> |
User-Agent: | Mutt/1.5.16 (2007-06-09) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Feb 15 09:37, klement2 wrote: > After excellently quick correction of pthread_kill when the argument > signal is zero > (by cgf), I have found another problem related to signal handling. The > code in attachment > demonstrates it ( because of pthread_kill, it must be run with > cygwin1-20080213.dll and newer ). > It seams that signal handlers for signals like SIGSEGV, SIGFPE are > called only once, This patch was necessary to get SEHs (and so Cygwin) working correctly on Windows 2008 Server. The new behaviour is covered by POSIX: http://www.opengroup.org/onlinepubs/009695399/functions/signal.html "If and when the function returns, if the value of sig was SIGFPE, SIGILL, or SIGSEGV or any other implementation-defined value corresponding to a computational exception, the behavior is undefined. Otherwise, the program shall resume execution at the point it was interrupted." Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |