update Dr.Memory suppression file for base_unittest sanity check test changes r245142

update Dr.Memory suppression file for base_unittest sanity check test changes r245142
TBR=earthdok@chromium.org
BUG=NONE

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245527

[zhaoqin, 2014-01-17 16:21:59]

Committed patchset #1 manually as r245527 (presubmit successful).

[earthdok, 2014-01-17 16:40:11]

On 2014/01/17 16:21:24, zhaoqin wrote:

How is that supposed to work? The new frame is above ReadUninitializedValue, but
you're adding a wildcard below it?

[zhaoqin, 2014-01-17 16:49:03]

On 2014/01/17 16:40:11, earthdok wrote:
> On 2014/01/17 16:21:24, zhaoqin wrote:
> 
> How is that supposed to work? The new frame is above ReadUninitializedValue,
but
> you're adding a wildcard below it?

the line: base_unittests.exe!*ReadUninitializedValue can match both top and
second frame, that's why Valgrind bot did not fail.
I make the suppression the same as valgrind's.

The suppression for valgrind memcheck:
{
   Memcheck sanity test 14 (malloc/read uninit).
   Memcheck:Uninitialized
   fun:*ReadUninitializedValue*
   ...
   fun:_ZN4base43ToolsSanityTest_AccessesToMallocMemory_Test8TestBodyEv
}

[earthdok, 2014-01-17 16:56:52]

lgtm