Bug #7703

Segfault in 1.9.3-p362, possibly threads related

Added by Tim Morgan almost 3 years ago. Updated almost 3 years ago.

Assignee:Usaku NAKAMURA
ruby -v:ruby 1.9.3p362 (2012-12-25 revision 38607) [x86_64-darwin12.2.1] Backport:


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

console-output.txt Magnifier - Output from ruby to STDOUT/STDERR after segfault (164 KB) Tim Morgan, 01/16/2013 10:25 AM

crashlog.txt Magnifier - OSX crash log (46.5 KB) Tim Morgan, 01/16/2013 10:25 AM

set-trace-func-tail.txt Magnifier - The last few set_trace_func outputs (2.65 KB) Tim Morgan, 01/16/2013 10:25 AM

gdb-output.txt Magnifier - Output from gdb `bt` command (5.71 KB) Tim Morgan, 01/16/2013 10:25 AM


#1 Updated by Eric Wong almost 3 years ago

"riscfuture (Tim Morgan)" ruby@timothymorgan.info wrote:

Issue #7703 has been reported by riscfuture (Tim Morgan).

Bug #7703: Segfault in 1.9.3-p362, possibly threads related

This is probably the same bug fixed in p363 (unreleased)
See https://bugs.ruby-lang.org/issues/7629

Hopefully a new 1.9.3 release will come soon (meanwhile you can
use SVN or the git mirror).

#2 Updated by Koichi Sasada almost 3 years ago

  • Assignee set to Usaku NAKAMURA
  • Target version set to 1.9.3

#3 Updated by Usaku NAKAMURA almost 3 years ago

  • Status changed from Open to Feedback

p374 will help you.

#4 Updated by Yui NARUSE almost 3 years ago

  • Target version changed from 1.9.3 to next minor

Also available in: Atom PDF