Possible bug in ruby VM

ruby-talk
1

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.

2

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.

···

On Dec 7, 2014, at 17:33, Arun kant sharma <iarunkant@gmail.com> wrote:

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.

3

fyi.
it also dumps in 2.1.5

···

On Mon, Dec 8, 2014 at 7:33 AM, Arun kant sharma <iarunkant@gmail.com> wrote:

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

4

I have created a bug report here Bug #10579: Segmentation fault at 0x00000000000000 - Ruby master - Ruby Issue Tracking System

···

On Mon, Dec 8, 2014 at 3:58 PM, Wayne Brissette <wbrisett@att.net> wrote:

On Dec 7, 2014, at 17:33, Arun kant sharma <iarunkant@gmail.com> wrote:

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.

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.

5

~> 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: atma@convalesco.org
URL: 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

···

On 8 Dec 2014, at 01:33, Arun kant sharma <iarunkant@gmail.com> wrote:

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.

6

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

···

On Mon, Dec 8, 2014 at 1:17 AM, botp <botpena@gmail.com> wrote:

On Mon, Dec 8, 2014 at 7:33 AM, Arun kant sharma <iarunkant@gmail.com> 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

--
[guy, jim].each {|him| remember.him do |as, often| as.you_can - without end}
http://blog.rubybestpractices.com/

7

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

···

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

On Mon, Dec 8, 2014 at 1:17 AM, botp <botpena@gmail.com> wrote:

On Mon, Dec 8, 2014 at 7:33 AM, Arun kant sharma <iarunkant@gmail.com> 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