How to suppress strncpy-param-overlap from a shared library?

2017-08-17 Thread Piotr Jachowicz
I'd like to suppress the error strncpy-param-overlap thrown fom some shared library. Even though I've addedd shared.so to suppression file, asan still reports it: ==5006==ERROR: AddressSanitizer: strncpy-param-overlap: memory ranges [0x60b0af90,0x60b0aff4) and [0x60b0af90, 0x60b

Extending LSAN to report where memory is leaked?

2017-08-17 Thread Eric Feng
Hi, For a memory leak, the current implementation of Leak Sanitizer (LSAN) reports in the code only the place where memory is dynamically allocated, but not where the actual leak happens. This make it sometimes difficult to locate the leak in a large complex program. One solution is to extend L

Re: Extending LSAN to report where memory is leaked?

2017-08-17 Thread 'Evgenii Stepanov' via address-sanitizer
Interesting idea, but I feel it would have very significant overhead. Basically, every time a region of memory is written or deallocated, we would need to scan the previous contents for anything that looks like a heap pointer and update metadata for those allocations. No need to track references -