X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; q=dns; s=default; b=nPSB CPk4K3aCy+fDzPrJQ55WAxn37TyK5jOP0FQcGVvFypWQMs1MLhTpoSxyyyGMcZv0 JCZWTw4pyPV1uWjZBzFYPH/Xg0jttBCawQ/DNxHzrqMpG+9U4YrDNd2zgD395F7V OyVQXnGGRwy3jHpp2iHEbuIyLb7PQu5Ae6g2J9Q= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; s=default; bh=RE0fI71abD 997nQtuuihE8gHaek=; b=iyxmPAM6qWgPtIYmBvGKj+NwYHs83R+nBfDMk6GI6P BWWqFgNkKCLrvPGiX2njp0hPPyWXPGeuHn7M+s6c3h0NzVwFopCN2qpZf94tISt/ WA9gIuOpsdCj61gniAi/MM1CjmH9PDVJyZpPW85VmYfN3Vu4syIWImlO2KBWPIvl c= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 X-Ironport-SBRS: 2.7 MIME-Version: 1.0 References: <20190130104421 DOT GC3912 AT calimero DOT vinschen DOT de> <20190130154804 DOT GJ3912 AT calimero DOT vinschen DOT de> <20190130212303 DOT GQ3912 AT calimero DOT vinschen DOT de> In-Reply-To: <20190130212303.GQ3912@calimero.vinschen.de> From: Dan Bonachea Date: Wed, 30 Jan 2019 19:11:29 -0500 Message-ID: Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes To: cygwin AT cygwin DOT com, Dan Bonachea Cc: "E. Madison Bray" , gasnet-devel AT lbl DOT gov Content-Type: text/plain; charset="UTF-8" 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