Interpreting ASAN leak detection output

Scott Kostyshak skostysh at lyx.org
Mon Sep 13 22:36:43 UTC 2021


I was just curious to compile LyX with address sanitizer options (-fsanitize=address). Now when I exit LyX I get the following:

----------------------
==352555==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 256 byte(s) in 1 object(s) allocated from:
    #0 0x7efe9a873c47 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
    #1 0x7efe9375d0c9  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x220c9)

Indirect leak of 32 byte(s) in 1 object(s) allocated from:
    #0 0x7efe9a873e17 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154
    #1 0x7efe9375d93e  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2293e)

SUMMARY: AddressSanitizer: 288 byte(s) leaked in 2 allocation(s).
----------------------

I don't know how to interpret the output. Does this mean the source of the leak is in libfontconfig.so? i.e., it's not LyX's fault?

Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20210913/3af0f3a5/attachment.asc>


More information about the lyx-devel mailing list