Suppression file appears to not be working

966 views
Skip to first unread message

David Barto

unread,
May 29, 2019, 2:37:06 PM5/29/19
to address-...@googlegroups.com
I’d prefer to suppress based on libcrypto, and it doesn’t take.

This is using gcc-7.2.0. This may be a too-old version of the compiler, if so, please let me know.

David

1041_ cat asan.suppression
interceptor_via_lib:libcrypto
interceptor_via_fun:CRYPTO_malloc
interceptor_via_fun:CRYPTO_realloc
1042_ export ASAN_OPTIONS=suppressions=$(pwd)/asan.suppression
1043_ azgctl -stop
Stopping database...

=================================================================
==5242==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 400 byte(s) in 2 object(s) allocated from:
#0 0x7fc7be8a98e0 in __interceptor_malloc ../../../../libsanitizer/asan/asan_malloc_linux.cc:62
#1 0x7fc7bd5f93b7 in CRYPTO_malloc (/usr/lib64/libcrypto.so.10+0x6e3b7)

Indirect leak of 7670 byte(s) in 141 object(s) allocated from:
#0 0x7fc7be8a98e0 in __interceptor_malloc ../../../../libsanitizer/asan/asan_malloc_linux.cc:62
#1 0x7fc7bd5f93b7 in CRYPTO_malloc (/usr/lib64/libcrypto.so.10+0x6e3b7)

Indirect leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x7fc7be8a9c90 in __interceptor_realloc ../../../../libsanitizer/asan/asan_malloc_linux.cc:75
#1 0x7fc7bd5f94a8 in CRYPTO_realloc (/usr/lib64/libcrypto.so.10+0x6e4a8)

SUMMARY: AddressSanitizer: 8134 byte(s) leaked in 144 allocation(s).

Konstantin Serebryany

unread,
May 30, 2019, 2:09:02 PM5/30/19
to address-sanitizer
please check this page for the exact syntax of leak suppressions: 

--
You received this message because you are subscribed to the Google Groups "address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to address-saniti...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/address-sanitizer/26BE0E98-7B93-4569-BA9C-74B7C5E8E2A4%40cambridgesemantics.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages