Re: [Valgrind-users] Frame-level wildcard not matching in suppression rule?

[Tom H. <to...@co...>]

On 05/02/14 22:21, Jeffrey Walton wrote:

> ==6516== Use of uninitialised value of size 8
> ==6516==    at 0x533B449: _x86_64_AES_encrypt_compact (in
> /usr/local/ssl/lib/libcrypto.so.1.0.0)
> ==6516==    by 0x533B6DA: fips_aes_encrypt (in
> /usr/local/ssl/lib/libcrypto.so.1.0.0)
> ==6516==    by 0x56FBC47: ??? (in /usr/local/ssl/lib/libcrypto.so.1.0.0)
> ==6516==    by 0x56FBD27: ??? (in /usr/local/ssl/lib/libcrypto.so.1.0.0)
> ==6516==    by 0x56FBE47: ??? (in /usr/local/ssl/lib/libcrypto.so.1.0.0)
> ==6516==    by 0xFFEFFFE17: ???

So this is the stack you are matching against.

> {
>     RAND_init_fips_1
>     Memcheck:Cond
>     ...
>     fun:RAND_init_fips
>     ...
> }

and this is one of the match rules, which uses a function that is not in 
the stack being matched.

> Any ideas what I'm doing wrong?

Yes, you're trying to match against the location where the memory is 
allocated, but suppression rules (except for leak suppressions) match 
against the stack at the point the error is detected.

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/