# Possible bug in ruby VM

**URL:** <https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363>\
**Category:** Ruby\
**Created:** [December 8, 2014, 12:34am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363 "2014-12-08T00:34:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [December 8, 2014, 12:34am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/1 "2014-12-08T00:34:38Z")

</div>

When I run

$ ruby -rresolv -e ‘ObjectSpace.each\_object { |obj| p obj }’

I experience a core dump, but if I run

$ ruby -e ‘ObjectSpace.each\_object { |obj| p obj }’

It does not happen. I am running

ruby 2.1.2p95 (2014-05-08 revision 45877) [x86\_64-linux]

Can anybody else confirm if this is a bug. I don’t have latest ruby to  
check against.

---

<div class="post-metadata">

**Author:** ![sanjayarun07](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@sanjayarun07](https://www.ruby-forum.com/u/sanjayarun07)\
**Post date:** [December 8, 2014, 1:18am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/2 "2014-12-08T01:18:06Z")

</div>

On Mon, Dec 8, 2014 at 7:33 AM, Arun kant sharma [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Can anybody else confirm if this is a bug. I don’t have latest ruby to check  
> against.

fyi.  
it also dumps in 2.1.5

---

<div class="post-metadata">

**Author:** ![sanjayarun07](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@sanjayarun07](https://www.ruby-forum.com/u/sanjayarun07)\
**Post date:** [December 8, 2014, 11:24am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/3 "2014-12-08T11:24:18Z")

</div>

On 12/8/2014 9:39 AM, Robert K. wrote:

> ruby 2.0.0p598 (2014-11-13) [x86\_64-cygwin]
> 
> Kind regards
> 
> robert

not dumping on Windows 8.1 x64  
?? ruby -v  
ruby 2.1.3p242 (2014-09-19 revision 47630) [x64-mingw32]

---

<div class="post-metadata">

**Author:** ![sanjayarun07](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@sanjayarun07](https://www.ruby-forum.com/u/sanjayarun07)\
**Post date:** [December 8, 2014, 9:40am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/4 "2014-12-08T09:40:34Z")

</div>

On Mon, Dec 8, 2014 at 1:17 AM, botp [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> On Mon, Dec 8, 2014 at 7:33 AM, Arun kant sharma [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:
> 
> > Can anybody else confirm if this is a bug. I don’t have latest ruby to check  
> > against.
> 
> fyi.  
> it also dumps in 2.1.5

Additional data point: it does not dump in my version:

$ ruby -v  
ruby 2.0.0p598 (2014-11-13) [x86\_64-cygwin]

Kind regards

robert

---

<div class="post-metadata">

**Author:** ![sanjayarun07](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@sanjayarun07](https://www.ruby-forum.com/u/sanjayarun07)\
**Post date:** [December 8, 2014, 11:28am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/5 "2014-12-08T11:28:36Z")

</div>

> It does not happen. I am running
> 
> ruby 2.1.2p95 (2014-05-08 revision 45877) [x86\_64-linux]
> 
> Can anybody else confirm if this is a bug. I don’t have latest ruby to check  
> against.

This is odd, it dumps on me too:

-e:1: [BUG] Segmentation fault at 0x00000000000000  
ruby 2.1.3p242 (2014-09-19 revision 47630) [x86\_64-darwin14.0]

Strange it would fail on come versions but not others.

---

<div class="post-metadata">

**Author:** ![sanjayarun07](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@sanjayarun07](https://www.ruby-forum.com/u/sanjayarun07)\
**Post date:** [December 8, 2014, 1:58pm UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/6 "2014-12-08T13:58:23Z")

</div>

I have created a bug report here [Bug #10579: Segmentation fault at 0x00000000000000 - Ruby master - Ruby Issue Tracking System](https://bugs.ruby-lang.org/issues/10579)

---

<div class="post-metadata">

**Author:** ![sanjayarun07](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/74df32/32.png) [@sanjayarun07](https://www.ruby-forum.com/u/sanjayarun07)\
**Post date:** [December 10, 2014, 6:59am UTC](https://www.ruby-forum.com/t/possible-bug-in-ruby-vm/233363/7 "2014-12-10T06:59:52Z")

</div>

> It does not happen. I am running
> 
> ruby 2.1.2p95 (2014-05-08 revision 45877) [x86\_64-linux]
> 
> Can anybody else confirm if this is a bug. I don’t have latest ruby to check  
> against.

~\> ruby -e '{[“foo”]=\>nil}; p Thread.current[: **recursive\_key**]’

-e:1: [BUG] Segmentation fault at 0x00000000000000  
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86\_64-darwin13.0]

dumps on mavericks (rvm ruby-2.1.2)

Panagiotis (atmosx) Atmatzidis

email: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
URL: [http://www.convalesco.org](http://www.convalesco.org)  
GnuPG ID: 0x1A7BFEC5  
gpg --keyserver pgp.mit.edu --recv-keys 1A7BFEC5

“As you set out for Ithaca, hope the voyage is a long one, full of  
adventure, full of discovery […]” - C. P. Cavafy
