From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20620 invoked by alias); 3 Mar 2014 17:06:32 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20598 invoked by uid 89); 3 Mar 2014 17:06:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 03 Mar 2014 17:06:31 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id D627452051E; Mon, 3 Mar 2014 18:06:28 +0100 (CET) Date: Mon, 03 Mar 2014 17:24:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Building libsigsegv on Cygwin64 Message-ID: <20140303170628.GA7236@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <530771A3.7000603@alice.it> <53136870.200@cornell.edu> <20140303150210.GC2469@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <20140303150210.GC2469@calimero.vinschen.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-03/txt/msg00053.txt.bz2 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1234 On Mar 3 16:02, Corinna Vinschen wrote: > On Mar 2 12:20, Ken Brown wrote: > [...] > > I found the problem (or at least I found *a* problem): There's a > > configure test "checking whether a fault handler according to POSIX > > works", which passes on 32-bit Cygwin but fails on 64-bit Cygwin. > > I'm attaching a file containing the configure test. Here's what > > happens in the 64-bit case: > >=20 > > $ gcc -o fault fault.c > > $ ./fault.exe > > $ echo $? > > 1 > >=20 > > In the 32-bit case, the exit code is 0. > >=20 > > I don't know if this indicates a Cygwin bug or something wrong with > > the test. >=20 > It indicates a Cygwin bug. Thanks for the report and the testcase. >=20 > The joke here is, the signal handler function gets called twice for the > same exception. Proof is that you can remove the second call to crasher > and still sigsegv_handler gets called twice. I just created a new snapshot which contains the fix. Would you mind to test it? It doesn't fix the fact that libsigsegv is missing 64 bit Windows/Cygwin support, of course... Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJTFLaUAAoJEPU2Bp2uRE+gB/kP/A3GUPtPT3GsIjgFFLtzBeWa +7zN929icVkvoK+0CMv3/9MlKJBZaMoFbi/A8RRA9ItZAhQDLpvKKvc4mUpVQ3vZ 9a3jOQb4RxHBwSlIMWEiwYbB0u/Nuj9DtigQ+tUVW3q5EJLwJFkrZZGZTNlywvuF /GzEEgwUubCdexk/la70yLFXC72VKVGKl95c/FGPUU0E0YT1KPCOR3vgUHIhIWQc CzC4Ylovh6677/4zaBu3r0wFBzgB7/O+io85i1W9RFDf6/HVdOLEEtoEO78qRVJ1 gkxaJofZs5RXEk4Ng6gcVNLaD+6VLB/Au+g5Tzja4gIEBRCSmjXbSmVLoYZ02XxV YrSbJ6MOXZoWRLSev980F2ptmol1cvUvwZ9RAfneTqMXHwasLXFoul2UYj5cqyYG QeCxmXs2eIiDDRMDy9tvtvtiW8moVg55VwVVYYSq83s4SidyKaN1GuMT9QHwNqaA lfyWm3e4+rKnT3w4KRvUEc7PAfJ5aJBO5a4bXrnDlJvpdmdrhP1p5stRWxLNcY8S CfXJduS91tXpNvlGiwk22mS4yEqCyUtuVKNOCvKEDapPTspWx8pbMgZcAcahxwlK IeWgE+5TuuJZDUrUt2PtqTAONLTiHoVv1VlI5Vr+8pBiHPzC3uNoy2/ZsIVg5NEB nulOlmwcb9GATYknWqpu =JgmC -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--