Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x7f4408236d28 in __interceptor_calloc
#1 0x56126c6f40a5 in dump_mmap_contiguous_heap
#2 0x56126c6f40a5 in dump_mmap_contiguous
#3 0x56126c6f40a5 in pdumper_load
#4 0x56126c47e1d2 in load_pdump
#5 0x56126c47e1d2 in main
#6 0x7f4406512b96 in __libc_start_main
SUMMARY: AddressSanitizer: 16 byte(s) leaked in 1 allocation(s).
On Sat, Aug 1, 2020 at 4:32 PM Philipp Stephani <[hidden email]> wrote:
> Am Sa., 1. Aug. 2020 um 22:24 Uhr schrieb Jeffrey Walton <[hidden email]>:
> > I don't have log files for Asan testing. The process is killed before
> > the log file gets written.
> > I think just about every test failed similar to:
> > =================================================================
> > ==18430==ERROR: LeakSanitizer: detected memory leaks
> Emacs intentionally leaks a lot of memory (like every system with a
> GC), so those tend to be false positives. If they still happen on
> master, consider suppressing them using __lsan_ignore_object or
How does one tell the good leaks from the bad leaks?