From: "ivoanjo (Ivo Anjo)" Date: 2022-08-22T11:18:32+00:00 Subject: [ruby-core:109629] [Ruby master Bug#18967] Segmentation fault in stackprof with Ruby 2.7.6 Issue #18967 has been updated by ivoanjo (Ivo Anjo). As pointed by @eregon I planned experimenting with this and raising it at some point -- the change in https://github.com/ruby/ruby/commit/0e276dc458f94d9d79a0f7c7669bde84abe80f21 did reorder things as far as the C source goes, but as far as I see it there really doesn't seem to be anything guaranteeing that the compiler won't reorder the write to ec->cfp with the actual initialization of the structure. So... yeah this doesn't seem particularly safe at this moment. (But it would be great if rb_profile_frames could indeed be made async-safe!) ---------------------------------------- Bug #18967: Segmentation fault in stackprof with Ruby 2.7.6 https://bugs.ruby-lang.org/issues/18967#change-98815 * Author: RubyBugs (A Nonymous) * Status: Third Party's Issue * Priority: Normal * ruby -v: ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Ruby 2.7.6 appears to have broken the stackprof gem, crashing on every run with a segmentation fault. Please see the following issues reported on stackprof: https://github.com/tmm1/stackprof/issues/185 https://github.com/tmm1/stackprof/issues/182 ---Files-------------------------------- stackprof_crash_ruby_2_7_6.txt.bz2 (69.1 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: