public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] manual: Drop the .so suffix in libc_malloc_debug description Date: Tue, 27 Jul 2021 02:25:31 +0000 (GMT) [thread overview] Message-ID: <20210727022531.9AB4B395C020@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=fb1621a88665ade96e7874046ed62b1cd2e7ff35 commit fb1621a88665ade96e7874046ed62b1cd2e7ff35 Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Tue Jul 27 07:54:46 2021 +0530 manual: Drop the .so suffix in libc_malloc_debug description All references to libraries in the manual are without the .so prefix, so do the same for libc_malloc_debug. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Diff: --- 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 a51ed42516..0b2b9c8795 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
reply other threads:[~2021-07-27 2:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210727022531.9AB4B395C020@sourceware.org \ --to=siddhesh@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).