Bug #10026
closedSegmentation fault
Description
The following segmentation fault is from running tests with RSpec on a somewhat large test suite. The results of the test are always printed before the segmentation fault.
/home/ubuntu/doximity/vendor/bundle/ruby/2.1.0/bin/rspec: [BUG] Segmentation fault at 0xfffffffffffffff9
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
-- Control frame information -----------------------------------------------
c:0001 p:0000 s:0002 E:0026f8 TOP [FINISH]
-- C level backtrace information -------------------------------------------
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x1b1495) [0x7ff465c8b495] vm_dump.c:685
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x707dc) [0x7ff465b4a7dc] error.c:307
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(rb_bug+0xb7) [0x7ff465b4bc57] error.c:334
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x138a36) [0x7ff465c12a36] signal.c:704
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7ff4657504a0]
/lib/x86_64-linux-gnu/libc.so.6(malloc_usable_size+0x7) [0x7ff46579ea37]
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(ruby_xfree+0x31) [0x7ff465b6ac91] gc.c:5943
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x1918f5) [0x7ff465c6b8f5] iseq.c:86
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x8ad8c) [0x7ff465b64d8c] gc.c:2061
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(rb_gc_call_finalizer_at_exit+0x1e3) [0x7ff465b6dc53] gc.c:2209
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(ruby_cleanup+0x1f2) [0x7ff465b52932] eval.c:129
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(ruby_run_node+0x25) [0x7ff465b52c25] eval.c:310
ruby() [0x4007db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7ff46573b76d]
ruby() [0x400809]
Updated by maletor (Ellis Berner) over 10 years ago
Here is the Other runtime information
Updated by normalperson (Eric Wong) over 10 years ago
eberner@gmail.com wrote:
Here is the Other runtime information
URL seems invalid.
-- C level backtrace information -------------------------------------------
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x1b1495) [0x7ff465c8b495] vm_dump.c:685
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x707dc) [0x7ff465b4a7dc] error.c:307
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(rb_bug+0xb7) [0x7ff465b4bc57] error.c:334
/home/ubuntu/.rvm/rubies/ruby-2.1.2/bin/../lib/libruby.so.2.1(+0x138a36) [0x7ff465c12a36] signal.c:704
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7ff4657504a0]
/lib/x86_64-linux-gnu/libc.so.6(malloc_usable_size+0x7) [0x7ff46579ea37]
Are you using LD_PRELOAD with an alternative malloc implementation which
does not provide malloc_usable_size?
That said, I'm not a big fan of Ruby calling malloc_usable_size because
it is fragile and makes it harder to switch mallocs.
Updated by nobu (Nobuyoshi Nakada) over 10 years ago
- Status changed from Open to Feedback
Probably malloc_usable_size
would access the pointer - 8, that means ruby_xfree
was called with (void *)1
.
Does this happen with the trunk and recent 2.1 snapshots as the target version is set to current: 2.2.0
?
Updated by maletor (Ellis Berner) about 10 years ago
The version I am experiencing the issue is with 2.1.2 and 2.1.3.
Updated by naruse (Yui NARUSE) almost 7 years ago
- Target version deleted (
2.2.0)
Updated by jeremyevans0 (Jeremy Evans) over 5 years ago
- Status changed from Feedback to Closed