From: "riscfuture (Tim Morgan)" Date: 2013-01-16T10:25:46+09:00 Subject: [ruby-core:51456] [ruby-trunk - Bug #7703][Open] Segfault in 1.9.3-p362, possibly threads related Issue #7703 has been reported by riscfuture (Tim Morgan). ---------------------------------------- Bug #7703: Segfault in 1.9.3-p362, possibly threads related https://bugs.ruby-lang.org/issues/7703 Author: riscfuture (Tim Morgan) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: ruby 1.9.3p362 (2012-12-25 revision 38607) [x86_64-darwin12.2.1] I can consistently cause a segfault in p362 that does not occur in p327 in my Rails project. From the stack trace it seems to be related to threads and `yield`. Unfortunately the code is for my company, Square, so it's a trade secret, but I can answer questions and run tests for you. In the attachments I have included verbose set_trace_func output, but the presence or absence of set_trace_func does not alter the crash. Mac OS X 10.8.2, Xcode command line tools, RVM -- http://bugs.ruby-lang.org/