X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<4A6854F8.4060204@byu.net>
Date:	Thu, 23 Jul 2009 06:18:00 -0600
From:	Eric Blake <ebb9 AT byu DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: [1.7] Updated: libsigsegv-2.6-1
References:	<4A678AC7 DOT 7090303 AT x-ray DOT at>
In-Reply-To:	<4A678AC7.7090303@x-ray.at>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Reini Urban on 7/22/2009 3:55 PM:
> I've updated libsigsegv to 2.6-1 and added a shared library in
> libsigsegv0-2.6-1
> I hope this solves the SEH corruption issue a little bit, as discussed
> at http://cygwin.com/ml/cygwin/2009-07/msg00639.html

Nope, 2.6 still has the SEH misuse bug.  But if you want to rebuild from a
git repository, my patches are now available to fix the SEH handling
(although I recommend building against cygwin snapshot 20090722 or newer;
building against cygwin 1.7.0-51 will detect that si_addr is still broken,
and pick up baggage related to cygwin 1.5 but not necessary for the latest
cygwin1.dll).  I only lightly tested a shared library with my patches.
Although the testsuite passed while using the shared library, I am still
wondering if there could be a problem at program shutdown if the shared
library is removed from memory without modifying its SEH handler back to
cygwin's handler, but I don't have any test case that provoked that scenario.

$ git pull git://repo.or.cz/libsigsegv/ericb.git master

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpoVPgACgkQ84KuGfSFAYCa1QCgg4IynLAagLWzsCzN5dusBouZ
ZWsAnj6B2J5t0gE1L5XYIsJwieUgpuIY
=fFk+
-----END PGP SIGNATURE-----

--
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

- Raw text -