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 wrote:
>
> On Sun, 22 Jun 2025, Daisuke Fujimura via Cygwin wrote:
>
> > The reproduction procedure could be simplified.
>
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 thre
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
Thank you for the advice.
I updated cygwin and ran again.
```
$ uname -srvmpio
CYGWIN_NT-10.0-22000-ARM64 3.6.1-1.x86_64 2025-04-09 11:31 UTC x86_64
unknown unknown Cygwin
(snip)
$ gdb /usr/bin/ruby
(gdb) set cygwin-exceptions on
(gdb) run /usr/bin/gem install -V --local --ignore-dependencies
--d
On 20/02/2025 15:33, Daisuke Fujimura via Cygwin wrote:
Reproduction:
- Use ruby-3.4.2-1 (test)
- Install gem containing native libraries
```
$ uname -srvmpio
CYGWIN_NT-10.0-22000 3.5.7-1.x86_64 2025-01-29 19:46 UTC x86_64
unknown unknown Cygwin
$ ruby -v
ruby 3.4.2 (2025-02-15 revision d2930f8e
5 matches
Mail list logo
