From: Eric Wong <normalperson@...>
Date: 2014-07-10T23:52:14+00:00
Subject: [ruby-core:63645] Re: [ruby-trunk - Bug #10026] Segmentation fault

eberner@gmail.com wrote:
> Here is the Other runtime information
> 
> https://gist.github.com/maletor/df43091aca5e9b7ee534

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.