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

• Status: Closed
• Assignee: usa (Usaku NAKAMURA)
• Target version: -
• ruby -v: ruby 1.9.3p362 (2012-12-25 revision 38607) [x86_64-darwin12.2.1]
• Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN

[riscfuture (Tim Morgan)]

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

[normalperson (Eric Wong)]

"riscfuture (Tim Morgan)" [e-mail] wrote:

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

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

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

[ko1 (Koichi Sasada)]

• Assignee set to usa (Usaku NAKAMURA)
• Target version set to 1.9.3

[usa (Usaku NAKAMURA)]

• Status changed from Open to Feedback

p374 will help you.

[naruse (Yui NARUSE)]

• Target version changed from 1.9.3 to 2.6

[naruse (Yui NARUSE)]

• Target version deleted (2.6)

[jeremyevans0 (Jeremy Evans)]

• Status changed from Feedback to Closed