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 LSAN to track references to dynamically allocated blocks, so it can report both places (where memory is allocated and where it’s lost) for a memory leak. I wonder if this idea has ever been brought up or discussed before? If yes, what's the reason for not not doing it. I understand doing so would require compiler instrumentation in addition to linking with the special LSAN library.
Thanks, -Eric Feng -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
