From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 40242 invoked by alias); 31 Jan 2019 00:12:23 -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 40220 invoked by uid 89); 31 Jan 2019 00:12:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=our X-HELO: fe3.lbl.gov Received: from fe3.lbl.gov (HELO fe3.lbl.gov) (131.243.228.52) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 31 Jan 2019 00:12:21 +0000 X-Ironport-SBRS: 2.7 Received: from mail-ot1-f69.google.com ([209.85.210.69]) by fe3.lbl.gov with ESMTP; 30 Jan 2019 16:12:09 -0800 Received: by mail-ot1-f69.google.com with SMTP id a19so642895otq.1 for ; Wed, 30 Jan 2019 16:12:09 -0800 (PST) Return-Path: Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com. [209.85.210.42]) by smtp.gmail.com with ESMTPSA id l5sm1235800oil.15.2019.01.30.16.12.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Jan 2019 16:12:08 -0800 (PST) Received: by mail-ot1-f42.google.com with SMTP id s13so1318221otq.4 for ; Wed, 30 Jan 2019 16:12:07 -0800 (PST) MIME-Version: 1.0 References: <20190130104421.GC3912@calimero.vinschen.de> <20190130154804.GJ3912@calimero.vinschen.de> <20190130212303.GQ3912@calimero.vinschen.de> In-Reply-To: <20190130212303.GQ3912@calimero.vinschen.de> From: Dan Bonachea Date: Thu, 31 Jan 2019 00:12:00 -0000 Message-ID: Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes To: cygwin@cygwin.com, Dan Bonachea Cc: "E. Madison Bray" , gasnet-devel@lbl.gov Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-01/txt/msg00305.txt.bz2 On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen wrote: > > > > Poking around further, I find that replacing the signal generation > > > > code in the test program for all cases with : > > > > > > > > pthread_kill(pthread_self(),sigid) > > > > > > > > generates compliant signal delivery behavior! > > > > > > Thanks, I fixed that in Cygwin. It will be part of the 3.0 release. > > > > I think I have a solution for the SISEGV misbehaviour. I have to > > test it a bit but this may make it into Cygwin 3.0 if all is well. > > Please try the latest developer snapshot from https://cygwin.com/snapshots/ > or the new 3.0.0-0.3 test release. I hope this fixes the problem > sufficiently. Hi Corinna - I've installed the 3.0.0-0.3 test release on my workstation and confirmed that it fixes all the reported misbehaviors in the test program. It also appears to fix the signal-related problems encountered in our multi-threaded production code. Thanks so much for the prompt fixes! -D -- 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