From: "mrkn (Kenta Murata)" <muraken@...>
Date: 2012-06-01T11:45:35+09:00
Subject: [ruby-core:45354] [ruby-trunk - Bug #5647][Closed] Possible use of uninitialized value in Init_bigdecimal


Issue #5647 has been updated by mrkn (Kenta Murata).

Status changed from Assigned to Closed

This is fixed by r35555
----------------------------------------
Bug #5647: Possible use of uninitialized value in Init_bigdecimal
https://bugs.ruby-lang.org/issues/5647#change-26942

Author: brixen (Brian Ford)
Status: Closed
Priority: Normal
Assignee: mrkn (Kenta Murata)
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://bugs.ruby-lang.org/