On 29/06/2011 1.08, Khem Raj wrote:
> On Thu, Jun 16, 2011 at 6:14 PM, wrote:
>> From: Maksim Rayskiy
>>
>> Unlike vsnprintf, vswprintf does not properly initialize locking
>> elements of FILE structure, which in some unfortunate cases can result
>> in lockups in _vfwprintf_internal.
>> Interest
On Thu, Jun 16, 2011 at 6:14 PM, wrote:
> From: Maksim Rayskiy
>
> Unlike vsnprintf, vswprintf does not properly initialize locking
> elements of FILE structure, which in some unfortunate cases can result
> in lockups in _vfwprintf_internal.
> Interesting, the initialization code was removed in
Any comments on this trivial patch?
On Thu, Jun 16, 2011 at 6:14 PM, wrote:
> From: Maksim Rayskiy
>
> Unlike vsnprintf, vswprintf does not properly initialize locking
> elements of FILE structure, which in some unfortunate cases can result
> in lockups in _vfwprintf_internal.
> Interesting, th
From: Maksim Rayskiy
Unlike vsnprintf, vswprintf does not properly initialize locking
elements of FILE structure, which in some unfortunate cases can result
in lockups in _vfwprintf_internal.
Interesting, the initialization code was removed in
2a915734a32c5aec9a6a76c13bcb074d30e64171 at the same