Issue #9874 has been updated by Nobuyoshi Nakada.

Status changed from Feedback to Third Party's Issue

Your `oj.bundle` extension library is linked against libruby.2.0.0.

~~~
4   libruby.2.1.0.dylib           	0x000000010b4128c9 sigsegv + 153 (signal.c:638)
5   libsystem_platform.dylib      	0x00007fff8de515aa _sigtramp + 26
6   ???                           	000000000000000000 0 + 0
7   libruby.2.0.0.dylib           	0x000000010d108810 st_init_strcasetable + 16 (st.c:247)
8   libruby.2.0.0.dylib           	0x000000010d00824e rb_enc_init + 110 (encoding.c:537)
9   libruby.2.0.0.dylib           	0x000000010d0092e5 rb_usascii_encoding + 21 (encoding.c:1186)
10  libruby.2.0.0.dylib           	0x000000010d0aa26a rb_intern2 + 26 (parse.y:10334)
11  libruby.2.0.0.dylib           	0x000000010d027c3f rb_define_module + 15 (class.c:622)
12  oj.bundle                     	0x000000010cfd7f21 Init_oj + 33 (oj.c:1696)
~~~

----------------------------------------
Bug #9874: Segmentation fault when loading rails console or rails server
https://bugs.ruby-lang.org/issues/9874#change-47029

* Author: Ivan Barrios
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.2p112 (2014-05-28 revision 46192) [x86_64-darwin13.0]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
OSX 10.9.3. This segmentation emerged only after upgrading from OSX 10.9.2 to 10.9.3. 
rails v4.0.3

Attached call stack and Gemfile/Gemfile.lock if those help to reproduce.

Also tried gem pristine --all, to force recompile of all gems with no success.

Seg fault is NOT encountered on the same system when running ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin13.0]



---Files--------------------------------
ruby-2.1.2p112_stack_trace.txt (65 KB)
Gemfile (2.92 KB)
Gemfile.lock (18.4 KB)
ruby_2014-05-27-091149_ivanbarrios.crash (24.4 KB)


-- 
https://bugs.ruby-lang.org/