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
on 2013-01-16 02:26
on 2013-01-16 02:43
"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 > 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).
on 2013-01-25 04:12
Issue #7703 has been updated by ko1 (Koichi Sasada). Assignee set to usa (Usaku NAKAMURA) Target version set to 1.9.3 ---------------------------------------- Bug #7703: Segfault in 1.9.3-p362, possibly threads related https://bugs.ruby-lang.org/issues/7703#change-35597 Author: riscfuture (Tim Morgan) Status: Open Priority: Normal Assignee: usa (Usaku NAKAMURA) Category: Target version: 1.9.3 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
on 2013-01-30 10:41
Issue #7703 has been updated by usa (Usaku NAKAMURA). Status changed from Open to Feedback p374 will help you. ---------------------------------------- Bug #7703: Segfault in 1.9.3-p362, possibly threads related https://bugs.ruby-lang.org/issues/7703#change-35725 Author: riscfuture (Tim Morgan) Status: Feedback Priority: Normal Assignee: usa (Usaku NAKAMURA) Category: Target version: 1.9.3 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
Enable email notification
Enable multi-page viewPlease log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.