My ticket, but text change proposed by Jakub Jelinek.
2022-12-26 Jonathan Grant <j...@jguk.org>
* gcc/doc/invoke.texi: Clarify LeakSanitizer in documentation
>From 2d70a3728536151c4c2f78b6c5d5281ce2233d43 Mon Sep 17 00:00:00 2001
From: Jonathan Grant <j...@jguk.org>
Date: Mon, 26 Dec 2022 20:46:23 +0000
Subject: [PATCH] Bugzilla 81649 clarify LeakSanitizer onlinedocs
Signed-off-by: Jonathan Grant <j...@jguk.org>
---
gcc/doc/invoke.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index da9ad1068fb..6743204adc0 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -16668,8 +16668,8 @@ operating on invalid memory addresses with non-call
exceptions
@item -fsanitize=leak
@opindex 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
--
2.37.2
