crypt32: Avoid reading unitialized variables (Coverity)
hverbeet at gmail.com
Wed Dec 14 07:54:54 CST 2011
On 14 December 2011 14:44, Michael Curran <curran.michaelp at gmail.com> wrote:
> Just a quick check, since Debian had a big kerfuffle when someone went
> and initialized variables in a crypto module, but is there any chance
> that those variables were left uninitialized on purpose?
Except for some TRACEs, I don't think these are actually read.
More information about the wine-devel