DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 536KwWqo1061601 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 536KwWqo1061601 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=UznPPIql X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F6E4385DDF9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1743973112; bh=pPsTIRrq4V/5p62ZYZbIsDCfLzoKq3WJOKzdYf7FYJ8=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=UznPPIqlQCgDf4Wpe7afG5f8sMtEXt4kFj0czHa0mqdPosazrh7dnIZAGRuRQhO/9 8tIQbXhXoYtgABUaNKNJ07N2DE4TG1GjJQskqaXDgDHdSw3psFJpdzo8RqOf+P1kC/ +CpgA/pIQRf/n+vmMfx/oPjrR9+Wg2kGwrousrK0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9B82A385DDF5 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 9B82A385DDF5 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743973088; cv=none; b=pNx91XicFzvC11ayGIrocnAEo9zH6mTzxBgtuknGbJ7U+SxWBvMjiknmE7HF/SWDfAvDug2WwUJSFWJTBEY3k+bjzLGNYwblXB/8dSA7XThMIHh+QnX7BivPakQEWrv5xDmwMCdnyT1aw14qKoAvVKru6PnJUOneKnmK+zVRzeI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743973088; c=relaxed/simple; bh=+z827TT4IHse7S4bb2lQ3Qr7uSpltG2GdpjF7N2R1cw=; h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature; b=Yd68IW78CVJsB32RKIHFgKo5uV3jdHnO4JvYFkzZOni8bQ7Z3HXASr/7trCuG48CIGVW4/Q7AbaQiDlmmc369uKnV1BB7kPgYoGLzOkG7t9mkvkehsc73X6B1QPvKGJXIuYdYRzfsNMv/w8LPlV2HypTO7npPIqGyWMf178Nruc= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9B82A385DDF5 Message-ID: <5f958daf-dfcc-4b46-8713-387a1d2113fa@SystematicSW.ab.ca> Date: Sun, 6 Apr 2025 14:58:05 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Python 3.12 testing Content-Language: en-CA To: cygwin AT cygwin DOT com References: <5cbe7341-f1b3-429c-a84a-fafe58408463 AT umbc DOT edu> Organization: Systematic Software In-Reply-To: <5cbe7341-f1b3-429c-a84a-fafe58408463@umbc.edu> X-Stat-Signature: wpkba4jurg1uhw87mahy4r7d3zc9jrub X-Rspamd-Server: rspamout06 X-Rspamd-Queue-Id: DBE552002D X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX1+KZC9LZ2hLFiTnG2ZyZUTfE+WfSVwcPuo= X-HE-Tag: 1743973086-972701 X-HE-Meta: U2FsdGVkX1+o/4uAigMImcThyO1ILDPcqMe683A2NMTA2YKw00Abmbnj63irXsxkzZ/ABRYLR2nqUy0wCjAoofpEWWtaYPZqit8iXmFwOC9SMkso5LaFl91/p4Tmw4r6vnMWgKFZjvBmt+V0H8b0mhMa6ANkF/FloTRRH/dXmbXeaS2kPMrtNEw09v8+FZkHPVd/7GU+FiGsnOm9H1oljTcApOjiV5egtG20vZB8pl+nqDdMgItaTyec086ekW1IZADdVTRAv8MNhs1jGkhHy/f3ToerraDhhanmzemJJEuaMl9dpBmduarjcBCAeVeFGOm2dkGlu2wq/gLXc1XdRdXZU8iqtbnU 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: Brian Inglis via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Brian Inglis Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 536KwWqo1061601 On 2025-04-06 14:32, dwes1--- via Cygwin wrote: > To the Python maintainer and anyone else testing Python 3.12: > > A few weeks ago, the python developer requested help with evaluating the Python > 3.12 release. > I downloaded the python312-test package, and worked out that > python -m test.test_threading -v > failed during the second test in the file, sometimes with an immediate segfault, > sometimes by hanging > until I tried to attach gdb, which immediately reported an empty stack and a > null stack pointer. > > Adding print calls to the test narrowed the point of failure to some time during > thread cleanup, > so I ran the test under gdb, adding breakpoints to pthread_exit and > pthread::exit, which caught > the test before the segfault, and displayed a stack working back to > pthread_wrapper, whose caller > was set to null.  Stepping through the function eventually reached a call to > ExitThread, then the > segfault with no reported stack. > > My current guess is that ExitThread somehow returns, leading to control falling > off the end of > pthread_wrapper and failing to return.  (This is rather more sensible than my > previous guess > that Python had somehow managed to call the NULL pointer recursively, and not > noticed until > gdb took a look at things)  I suppose I could try to compile Cygwin with an > error message after > ExitThread to see if that prints, but I am otherwise out of ideas. > > I first checked this around January on a Windows 10 machine from 2016, then on a > machine from > within the last year that is says it is also Windows 10. > > I hope this helps Thanks for helping! Have you tried running under strace and looking at the output from: $ strace -o python-312-test-threading.strace python -m test.test_threading -v or $ strace -o python-312-test-threading-hung.strace -p PID -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut -- Antoine de Saint-Exupéry -- 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