From: nobu@...
Date: 2014-12-09T01:16:43+00:00
Subject: [ruby-core:66752] [ruby-trunk - Bug #10579] [Closed] Segmentation fault at 0x00000000000000

Issue #10579 has been updated by Nobuyoshi Nakada.

Status changed from Open to Closed
% Done changed from 0 to 100

Applied in changeset r48744.

----------
thread.c: get rid of invalid ID symbol

* eval.c (rb_frame_last_func): return the most recent frame method
  name.
* thread.c (recursive_list_access): use the last method name,
  instead of the current method name which can be unset in some
  cases, not to use a symbol by the invalid ID.
  [ruby-core:66742] [Bug #10579]

----------------------------------------
Bug #10579: Segmentation fault at 0x00000000000000
https://bugs.ruby-lang.org/issues/10579#change-50340

* Author: Arun Kant Sharma
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: core
* Target version: current: 2.2.0
* ruby -v: ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
* Backport: 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
Following script cause a Segmentation fault

~~~
$ ruby -rresolv -e 'ObjectSpace.each_object { |obj| p obj }' > temp.output
~~~
But this one not

~~~
$ ruby -e 'ObjectSpace.each_object { |obj| p obj }' > temp.output
~~~

---Files--------------------------------
rubyerror.output (18.7 KB)


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