http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59061
--- Comment #16 from Sergey Matveev <earthdok at google dot com> --- (In reply to Kostya Serebryany from comment #11) > > Easily doable of course, but we should create liblsan as shared > > library in that case too. What combination of those do you allow? I mean, > > is > > -fsanitize=address,leak allowed (and only links -lasan?), etc.? > > Sergey, please answer here (and make sure this is documented) Under the current behavior -fsanitize=address,leak is equivalent to -fsanitize=address. We've considered other options, such as making -fsanitize=leak change the default run-time behavior (currently the ASan runtime always has leak detection runtime-disabled by default, whereas the standalone LSan runtime always has it enabled). But we never arrived at anything sensible.
