From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] manual: Drop the .so suffix in libc_malloc_debug description
Date: Thu, 22 Jul 2021 21:57:33 +0530 [thread overview]
Message-ID: <20210722162733.3185678-1-siddhesh@sourceware.org> (raw)
All references to libraries in the manual are without the .so prefix,
so do the same for libc_malloc_debug.
---
manual/memory.texi | 6 +++---
manual/tunables.texi | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/manual/memory.texi b/manual/memory.texi
index 69c8894602..b91c6fd70c 100644
--- a/manual/memory.texi
+++ b/manual/memory.texi
@@ -1255,7 +1255,7 @@ environment variable @env{MALLOC_ARENA_MAX} to the desired value.
You can ask @code{malloc} to check the consistency of dynamic memory by
using the @code{mcheck} function and preloading the malloc debug library
-@file{libc_malloc_debug.so} using the @var{LD_PRELOAD} environment variable.
+@file{libc_malloc_debug} using the @var{LD_PRELOAD} environment variable.
This function is a GNU extension, declared in @file{mcheck.h}.
@pindex mcheck.h
@@ -1368,7 +1368,7 @@ used which is designed to be tolerant against simple errors, such as
double calls of @code{free} with the same argument, or overruns of a
single byte (off-by-one bugs). Not all such errors can be protected
against, however, and memory leaks can result. Like in the case of
-@code{mcheck}, one would need to preload the @file{libc_malloc_debug.so}
+@code{mcheck}, one would need to preload the @file{libc_malloc_debug}
library to enable @code{MALLOC_CHECK_} functionality. Without this
preloaded library, setting @code{MALLOC_CHECK_} will have no effect.
@@ -1575,7 +1575,7 @@ penalties for the program if the debugging mode is not enabled.
The @code{mtrace} function provides a way to trace memory allocation
events in the program that calls it. It is disabled by default in the
library and can be enabled by preloading the debugging library
-@file{libc_malloc_debug.so} using the @code{LD_PRELOAD} environment
+@file{libc_malloc_debug} using the @code{LD_PRELOAD} environment
variable.
When the @code{mtrace} function is called it looks for an environment
diff --git a/manual/tunables.texi b/manual/tunables.texi
index e264e9150c..658547c613 100644
--- a/manual/tunables.texi
+++ b/manual/tunables.texi
@@ -114,7 +114,7 @@ following tunables in the @code{malloc} namespace:
@deftp Tunable glibc.malloc.check
This tunable supersedes the @env{MALLOC_CHECK_} environment variable and is
identical in features. This tunable has no effect by default and needs the
-debug library @file{libc_malloc_debug.so} to be preloaded using the
+debug library @file{libc_malloc_debug} to be preloaded using the
@code{LD_PRELOAD} environment variable.
Setting this tunable to a non-zero value less than 4 enables a special (less
--
2.31.1
next reply other threads:[~2021-07-22 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 16:27 Siddhesh Poyarekar [this message]
2021-07-27 2:03 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210722162733.3185678-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).