Project

General

Profile

Actions
Copy link

Bug #7703

closed

Segfault in 1.9.3-p362, possibly threads related

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

Added by riscfuture (Tim Morgan) almost 13 years ago. Updated over 6 years ago.

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
[ruby-core:51456]

Description

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

Files

Download all files
console-output.txt (164 KB) console-output.txt Output from ruby to STDOUT/STDERR after segfault riscfuture (Tim Morgan), 01/16/2013 10:25 AM
crashlog.txt (46.5 KB) crashlog.txt OSX crash log riscfuture (Tim Morgan), 01/16/2013 10:25 AM
set-trace-func-tail.txt (2.65 KB) set-trace-func-tail.txt The last few set_trace_func outputs riscfuture (Tim Morgan), 01/16/2013 10:25 AM
gdb-output.txt (5.71 KB) gdb-output.txt Output from gdb `bt` command riscfuture (Tim Morgan), 01/16/2013 10:25 AM
Actions
Copy link

Also available in: PDF Atom