Bug #5647: Possible use of uninitialized value in Init_bigdecimal

• Status: Closed
• Assignee: mrkn (Kenta Murata)
• Target version: -
• ruby -v: ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin10.8.0]

[brixen (Brian Shirai)]

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

[mrkn (Kenta Murata)]

• Assignee set to mrkn (Kenta Murata)

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Assigned

[mrkn (Kenta Murata)]

• Status changed from Assigned to Closed

This is fixed by r35555