From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11445 invoked by alias); 26 Apr 2018 10:45:08 -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 11067 invoked by uid 89); 26 Apr 2018 10:45:05 -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=H*R:D*cygwin.com, H*F:D*nl 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 10:45:03 +0000 Received: from tmp.zuPfMfpv4f ([83.162.234.136]) by smtp-cloud9.xs4all.net with ESMTPSA id BeOZfWnigSQicBeOafWa83; Thu, 26 Apr 2018 12:45:00 +0200 Date: Thu, 26 Apr 2018 10:45:00 -0000 Message-ID: From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Bug: Synchronous signals broken on Cygwin 64 References: In-Reply-to: Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-CMAE-Envelope: MS4wfNGcYhKwFsBJtQlO1X0H50BRsEcYI3QJFQMGR3elQTNQzr3S+DheqrArjFh194yIDc9P2zhgZRLStN6pHi+aDnOPG1dAG6PvJrnGMQ9rIUv68gj1rbnj uHIP/ZMqni851w07FoL3frBj+mB0x5/eOkcO7lKEY/oejbhcmTQgKX5dAjHJpL4tE5lRJrg8P7kDmw== X-SW-Source: 2018-04/txt/msg00318.txt.bz2 On Thu, 26 Apr 2018 09:57:59, Thomas Zimmermann wrote: > Hello mailing list, > > I noticed that synchronous signals (e.g., SIGSEGV, SIGFPE) appear to be > broken on 64-bit Cygwin systems. I could not find additional information > on the mailing list. If this is not already a known problem, you'll find > some analysis below. > > I use Cygwin DLL 2.10 with all packages up-to-date. My test system runs > Windows 7. > > 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: .. uhm, unless SA_RESETHAND (sa_flags) has been specified, I expect the handler to be invoked again and again ... And that is what I observe on Linux ... > 1) Generating a synchronous signal on the main thread, makes the signal > handler enter an endless loop. The attached test 'syncsig.c' illustrates > this. > > 2) Generating a synchronous signal on an additional POSIX thread ignores > the installed signal handler entirely. The handler does not run and the > program gets terminated immediately. The attached test 'syncsig_mt.c' > illustrates this. Yes, this behaviour is wrong ... Henri -- 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