Comment #11 on issue 6522 by [email protected]: [UMR] Uninitialized memory read in fwrite_nolock http://code.google.com/p/chromium/issues/detail?id=6522
I'm seeing this in valgrind, too, now. How are you suppressing it in purify? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
