DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 526J3PHd568216 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 526J3PHd568216 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=wUEBUUhd X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 51E7E3858C2C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1741287803; bh=zPF5+8mLo2Xng1JPw8n0Fvw1oqTGOYnj5aA2rsv6qGI=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=wUEBUUhdHua8sDwFFo7SZH6y2jCJs5w/DjAfqdClMBhNI8DMqjqtzVQkCIvBowz/O hsC0EVd/Ak+YVoGtSUdW/AtSclVxAEgAeAAyqP3ALn/HKxj8GNWOQ9uO5gJVM/IWLw VybyZtcbabeMQGhhy+jG5WRJ1RGn642CsjUCPLaA= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3132F3858D20 Date: Thu, 6 Mar 2025 20:02:56 +0100 To: cygwin AT cygwin DOT com Subject: Re: cygwin 3.6.0: No signals received after swapcontext() is used Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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