From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99025 invoked by alias); 26 Apr 2018 11:02:12 -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 99016 invoked by uid 89); 26 Apr 2018 11:02:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=recalled, Best X-HELO: lb2-smtp-cloud9.xs4all.net Received: from lb2-smtp-cloud9.xs4all.net (HELO lb2-smtp-cloud9.xs4all.net) (194.109.24.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Apr 2018 11:02:01 +0000 Received: from tmp.y62gnNuY5i ([83.162.234.136]) by smtp-cloud9.xs4all.net with ESMTPSA id Bef0fxwTMbfBnBef1fRrh3; Thu, 26 Apr 2018 13:01:59 +0200 Date: Thu, 26 Apr 2018 11:02:00 -0000 Message-ID: <26e03635c83cba20a1ef68e238e41ec2@smtp-cloud9.xs4all.net> From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Bug: Synchronous signals broken on Cygwin 64 References: <4a3b47db-fcdb-85f0-ec80-4cffcb7c495a@users.sourceforge.net> In-Reply-to: <4a3b47db-fcdb-85f0-ec80-4cffcb7c495a@users.sourceforge.net> Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-CMAE-Envelope: MS4wfOgaUrCklKxJDo/c6wxeuK4sg3VoU9EQS4h0YrJJB3XzaSvhxgelA7eORV3Mkn796R3ToW90bLv4fTSipKnGp0imRUGj7snVxfI4MTBbKeaEpICra2tI rOn4rUvQBLinHEcIVsx4KTtizLQLhQrNgYTOVlh2Gm40aB0aiWWqNhdjF2xHrd/AiAIVDEtAJl72qg== X-SW-Source: 2018-04/txt/msg00321.txt.bz2 On Thu, 26 Apr 2018 12:52:54, Thomas Zimmermann wrote: > Hi > > Am 26.04.2018 um 12:45 schrieb Houder: > >> The expected behavior is that an installed signal handler runs exactly > >> once for a signal and the OS terminates the program if the handler > >> returns. This works on 32-bit Cygwin. From my observation, Cygwin 64 > >> differs in the follow ways: > >=20 > > .. uhm, unless SA_RESETHAND (sa_flags) has been specified, I expect the > > handler to be invoked again and again ... > > What I mean is that the installed signal handler is re-called constantly > for the same HW exception (div-by-zero in this case). It is as if > there's an endless loop around the signal-handler function. After the invocation of the handler, the program continues with the code that attempts 'to divide by zero'. As result of that, the handler is invoked again. Henri > Best regards > Thomas -- 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