From: "dafiku (dafi harisy)" <dafi@...>
Date: 2012-10-23T14:21:09+09:00
Subject: [ruby-core:48156] [Backport93 - Backport #6618] Seg Fault when printing thread.keys


Issue #6618 has been updated by dafiku (dafi harisy).


Everlastingly, an issue with the intention of I am passionate in this vicinity. I be inflicted with looked for in rank of this feature for the last numerous hours. Your locate is greatly valued.
http://www.yourhousecontents.com/
http://www.electroscanogram.com/
http://www.videophototravel.info/
http://www.supershinelaundry.com/
http://www.ywor.info/
http://www.bicity.info/
http://www.ubidyne.info/
----------------------------------------
Backport #6618: Seg Fault when printing thread.keys
https://bugs.ruby-lang.org/issues/6618#change-31312

Author: cantregister (Why Cantiregister)
Status: Closed
Priority: Normal
Assignee: 
Category: 
Target version: 


This is very easy to reproduce:

require 'bigdecimal'

for thr in Thread.list
 puts thr.keys
end

Somehow a key is introduced to the thread with the object ID of 8.

Attempting to inspect or to_s this key results in a seg fault.

1.9.3p194 :001 > ObjectSpace._id2ref(8)
RangeError: 0x00000000000008 is not symbol id value

It is not clear how this object is created or inserted into the Thread. 


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