On Sat, Sep 23, 2017 at 12:13:16PM -0400, Jeff King wrote:
> In theory you should be able to just add "log_path=/tmp/lsan/output" to
> that, which should put all the logs in a convenient place (and stop the
> extra output from confusing any tests which capture stderr). But I can't
> seem to get log_path to do anything, contrary to the documentation.
>
> Doing log_to_syslog=1 does work for me. I'm not sure if it's a bug or
> I'm holding it wrong. But it does seem like it should be possible to do
> what you want.
Hrm. log_path doesn't seem to work for me directly from LSAN_OPTIONS.
But if you compile with ASan, it _does_ work from there. That seems like
a bug from my reading of the documentation, but maybe I'm missing
something.
Anyway, doing:
ASAN_OPTIONS=detect_leaks=1:abort_on_error=0:exitcode=0:log_path=/tmp/lsan/output \
make SANITIZE=address,leak test
should pass the whole suite and give you a host of files to analyze.
I'm not sure of the best way to count things. Surely many of these are
the same leak over and over. One way to visualize is to look at the
unique entries at each level of the call stack:
show() {
level=$1
perl -lne 'print $1 if /#'$level' .*? in (.*)/' * |
sort | uniq -c | sort -rn
}
Level 0 isn't that interesting, it's just malloc:
$ show 0
27217 realloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xd9f20)
23297 __interceptor_strdup (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x74490)
19370 malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xd9b70)
12105 __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xd9d48)
And level 1 is just our allocators:
$ show 1
28321 xrealloc /home/peff/compile/git/wrapper.c:138
25199 xstrdup /home/peff/compile/git/wrapper.c:44
18856 do_xmalloc /home/peff/compile/git/wrapper.c:60
12664 xcalloc /home/peff/compile/git/wrapper.c:160
660 __getdelim (/lib/x86_64-linux-gnu/libc.so.6+0x682b7)
But level 2 starts to get interesting (and is too big to copy here).
Some of them are direct sources of leaks. But others like strbuf_grow()
are yet another level of indirection, and you'd want to jump to level 3
or 4.
If you want the "real" source of the leak, probably you'd have to mark
certain functions as uninteresting and keep walking each stack trace
until you find an interesting function to report.
-Peff
