Date: Fri, 19 May 2023 11:20:15 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 271490] Deadlock between _rtld_atfork_pre and _thr_attr_init Message-ID: <bug-271490-13406-9xBiimrCNK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271490-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-271490-13406@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271490 --- Comment #5 from KJ Tsanaktsidis <kj@kjtsanaktsidis.id.au> --- > Can you please provide me the stand-alone ruby program that demonstrates = the problem in non-disputable way, and the exact instructions how to launch it? Unfortunately I still haven't been able to isolate the problem outside of t= he actual Ruby test harness.... so this is all a bit involved. I've been tryin= g to develop a minimal reproduction (with either C or Ruby) but I haven't had any luck so far. * You'll need `git`, `autoconf`, `automake`, `bison`, `m4`, `libffi`, `libunwind`, and `libyaml`. * Clone my Ruby fork: `git clone https://github.com/KJTsanaktsidis/ruby.git` * Check out this commit (includes some _other_ fixes necessary to surface t= his problem): `git checkout d5471e6e1e8b81d7c7e960538d138868db0e0707` * `autoreconf -fi` * `./configure` (I don't think any particular flags are needed) * `make` Then, use the built ruby to run this particular test in a loop, until eventually it hangs: ``` while ./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb --extout=3D.ex= t -- ./test/runner.rb test/ruby/test_process.rb -n test_daemon_no_threads; do ec= ho "ok"; done; ``` --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271490-13406-9xBiimrCNK>