public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page malloc.3
Date: Sun, 4 Dec 2022 13:23:23 +0100	[thread overview]
Message-ID: <3aa271a7-b566-7ffd-1dd8-c11f347bfa08@gmail.com> (raw)
In-Reply-To: <20221204090710.GA301@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]



On 12/4/22 10:07, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    preserve errno → preserve I<errno>
> 
> "If your program uses a private memory allocator, it should do so by"
> "replacing B<malloc>(), B<free>(), B<calloc>(), and B<realloc>().  The"
> "replacement functions must implement the documented glibc behaviors,"
> "including I<errno> handling, size-zero allocations, and overflow checking;"
> "otherwise, other library routines may crash or operate incorrectly.  For"
> "example, if the replacement I<free>()  does not preserve errno, then"
> "seemingly unrelated library routines may fail without having a valid reason"
> "in I<errno>.  Private memory allocators may also need to replace other glibc"
> "functions; see \"Replacing malloc\" in the glibc manual for details."

Fixed.  Thanks.

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-04 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04  9:07 Issue in man page malloc.3 Helge Kreutzmann
2022-12-04 12:23 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-08-31 12:08 ` Alejandro Colomar

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=3aa271a7-b566-7ffd-1dd8-c11f347bfa08@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /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