DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 526J3PHd568216
Date: Thu, 6 Mar 2025 20:02:56 +0100
To: cygwin@cygwin.com
Subject: Re: cygwin 3.6.0: No signals received after swapcontext() is used
Message-ID: <Z8nxYCxthcsMVqzL@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <ec6e2050-953f-0d47-c385-cfa598566291@t-online.de>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <ec6e2050-953f-0d47-c385-cfa598566291@t-online.de>
Precedence: list
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

On Mar  6 13:24, Christian Franke via Cygwin wrote:
> Found because 'stress-ng --context 1 ...' always hangs.
> 
> The attached testcase uses the example from Linux swapcontext(3) to call the
> context functions.

Just tested with 3.5.3 and it doesn't work there, either.

So yeah, it's a bug, but it's not a 3.6 regression and of minor
importance.  We can look into that for 3.7.


Thanks,
Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple