From: Jonathan Grant Date: Tue, 7 Mar 2023 21:57:44 +0000 (+0000) Subject: docs: Clarify LeakSanitizer in documentation [PR81649] X-Git-Tag: basepoints/gcc-14~672 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c5c4fdaccdf444632c9872537b6026dc6758a952;p=thirdparty%2Fgcc.git docs: Clarify LeakSanitizer in documentation [PR81649] gcc/ChangeLog PR sanitizer/81649 * doc/invoke.texi (Instrumentation Options): Clarify LeakSanitizer behavior. --- diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 2da68802356e..beb606fcd1bd 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -16750,8 +16750,8 @@ operating on invalid memory addresses with non-call exceptions @opindex fsanitize=leak @item -fsanitize=leak Enable LeakSanitizer, a memory leak detector. -This option only matters for linking of executables and -the executable is linked against a library that overrides @code{malloc} +This option only matters for linking of executables. +The executable is linked against a library that overrides @code{malloc} and other allocator functions. See @uref{https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer} for more details. The run-time behavior can be influenced using the