Just to make sure: all you are suggesting is to change the default value(s)
of flag(s), right?
I am reluctant to change the defaults here because core dumps are rarely
useful with asan reports and because they will cause more trouble then is
worth it (atexit timeout, disk full, etc)
--kcc
On
I think the usual solution is to have an option in the program to disable the
custom allocator and use system malloc/free instead, and run ASan/LSan in this
mode. Far from ideal, but seems to work well in practice. Does that not fit
in your scenario?
Kuba
> On 27 Jul 2017, at 13:42, Francis
Hi all,
Is there currently a good way to run ASan/LSan on a program using a custom
allocator (for example, tcmalloc)? I couldn't find any solutions in the
current code other than manually adding some extra interceptors locally (in
the tcmalloc case those would be things like tc_malloc and
Hi all,
Currently core dumps are disabled on 64-bit platforms. This decisions
come from old times when 16 TB shadow memory was included in coredump.
Nowadays we have use_madv_dontdump (enabled by default) which keeps
size of core file reasonable. Perhaps we can disable disable_coredump
on all
