From: Brian Ford <brixen@...>
Date: 2011-11-18T17:52:24+09:00
Subject: [ruby-core:41133] [ruby-trunk - Bug #5647][Open] Possible use of uninitialized value in Init_bigdecimal


Issue #5647 has been reported by Brian Ford.

----------------------------------------
Bug #5647: Possible use of uninitialized value in Init_bigdecimal
http://redmine.ruby-lang.org/issues/5647

Author: Brian Ford
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin10.8.0]


I see the following call chain in bigdecimal.c

Init_bigdecimal -> VpInit -> VpAlloc -> VpGetPrecLimit -> rb_thread_local_aref with id_BigDecimal_precision_limit

The call to VpInit occurs before the call to set the value of id_BigDecimal_precision_limit in Init_bigdecimal.

So it appears that a thread local is set with the key of an uninitialized C value, if I'm following correctly.

Thanks,
Brian


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