X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A60FC49.1060808@gmail.com> Date: Fri, 17 Jul 2009 23:33:45 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: fun? with libsigsegv References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Eric Blake wrote: > This post is so cgf can exhale his bated breath from his recent commit: > That is, libsigsegv no longer causes an unwanted abort. And the latest > libsigsegv.git package still passes 'make check'. So in other words, it looks > like you fixed a real bug, and without causing any regressions to libsigsegv > (at least, none identified so far, although the upstream testsuite could > probably test more cases)! Thanks! From the patch: > + [ ... ] This could present > + a problem if some previous exception handler tries to do things that are > + better left to Cygwin. [ ... ] Sounds like libsigsegv knows what it's doing and is only doing what it should and correctly leaving to Cygwin things best left to Cygwin. (Plus a quick browse of the source made reinforced that impression; it doesn't replace but carefully chains in front of the cygwin exception handler and passes through any exceptions it doesn't eat.) cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple