DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 55NAF5Ix3611552
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 24FF43856DEE
MIME-Version: 1.0
References: <CAA3frXTFnLSF2HzB5Z278=5J0bsOGRcRmqyv+7qcr3-QGmKbBw AT mail DOT gmail DOT com>
 <7a8fd4a7-e07c-4d09-9741-72d3b2b27b06 AT dronecode DOT org DOT uk>
 <CAA3frXQiMLSLOpj2CE1toQEO=fR26HB59h2H4mBy5ykwDC-_RA AT mail DOT gmail DOT com>
 <CAA3frXSNjcCPoXw_1XXdMWsZB9-QkSH2qjL=m52xj9hmrG9Trg AT mail DOT gmail DOT com>
 <f679ed10-e7de-f7b4-3142-ecafa89819aa AT jdrake DOT com>
In-Reply-To: <f679ed10-e7de-f7b4-3142-ecafa89819aa@jdrake.com>
Date: Mon, 23 Jun 2025 19:14:00 +0900
Message-ID: <CAA3frXR_aV+LtHUKjcuA6S9Co5rJTRN7PeV7Da-jNEgnytqrKw@mail.gmail.com>
Subject: Re: SIGSEGV in pthread_testcancel() likely due to NULL TLS access
 (Re: A process spawned inside gem command running on latest ruby segfaults)
To: cygwin AT cygwin DOT com
From: Daisuke Fujimura via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Daisuke Fujimura <booleanlabel AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

I tried running a ruby program with openssl-3.0.16-2, and confirmed
that the SIGSEGV no longer occurs. Thank you for the advice.

On Mon, Jun 23, 2025 at 2:04 AM Jeremy Drake <cygwin AT jdrake DOT com> wrote:
>
> On Sun, 22 Jun 2025, Daisuke Fujimura via Cygwin wrote:
>
> > The reproduction procedure could be simplified.
> >
> > A segmentation fault (SIGSEGV) occurs when running a Ruby script using
> > Ruby 3.4.2 (test package) on Cygwin 3.6.3-1 (x86_64), where Thread.new
> > is used to require 'openssl' inside a thread.
> >
> > The crash path leads from OpenSSL’s OPENSSL_thread_stop() to
> > CRYPTO_THREAD_write_lock() and then pthread_rwlock_wrlock(), which
> > invokes pthread_testcancel(). At that point, a NULL pointer
> > dereference seems to occur, possibly during access to TLS data.
> >
> > Thread 8 "repro.rb:1" received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 7380.0x25e4]
> > 0x0000000000000000 in ?? ()
> > (gdb) where
> > #0 0x0000000000000000 in ?? ()
> > #1 0x00007ffe4ad2a0e4 in pthread_testcancel () at
> > /usr/src/debug/cygwin-3.6.3-1/winsup/cygwin/thread.cc:399
> > #2 pthread_rwlock_wrlock (rwlock=0xa002a9010) at
> > /usr/src/debug/cygwin-3.6.3-1/winsup/cygwin/thread.cc:4352
> > #3 0x00007ffe4ae0b0d4 in _sigfe () at sigfe.s:35
> > #4 0x00000003ff54e3f9 in CRYPTO_THREAD_write_lock (lock=<optimized
> > out>) at crypto/threads_pthread.c:110
> > #5 0x00000003ff541922 in init_thread_remove_handlers
> > (handsin=handsin AT entry=0x0) at crypto/initthread.c:178
> > #6 0x00000003ff541d43 in OPENSSL_thread_stop () at crypto/initthread.c:235
> > #7 0x00000003ff53fdd3 in DllMain (hinstDLL=<optimized out>,
> > fdwReason=<optimized out>, lpvReserved=<optimized out>)
> > at crypto/dllmain.c:38
> > #8 0x00007ffe8f2fd6ac in ?? ()
> > #9 0x00007ffe8f38b590 in ?? ()
> > #10 0x00007ffe8f38b590 in ?? ()
> > #11 0x0000000000000000 in ?? ()
>
> This should be fixed by test release openssl-3.0.16-2
> (https://cygwin.com/pipermail/cygwin-announce/2025-May/012341.html).  I
> don't know what the plan is for making that stable, or getting a patch
> upstream.

-- 
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