public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/17924] 'free' should not set errno
Date: Sat, 19 Dec 2020 22:02:47 +0000	[thread overview]
Message-ID: <bug-17924-131-iOSCwJiwr4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17924-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17924

--- Comment #4 from Bruno Haible <bruno at clisp dot org> ---
I believe there is also another code path that can lead to free() setting
errno.

Namely, when glibc is not configured with --disable-experimental-malloc,
USE_TCACHE gets defined and enables this code path:
__libc_free -> malloc.c:3147 -> MAYBE_INIT_TCACHE -> malloc.c:3033 ->
tcache_init -> malloc.c:3007 -> _int_malloc -> malloc.c:3580 -> sysmalloc

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-12-19 22:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  0:06 [Bug malloc/17924] New: " eggert at gnu dot org
2015-02-06  9:19 ` [Bug malloc/17924] " fweimer at redhat dot com
2020-12-19 19:30 ` bruno at clisp dot org
2020-12-19 21:05 ` eggert at cs dot ucla.edu
2020-12-19 22:02 ` bruno at clisp dot org [this message]
2020-12-19 23:31 ` eggert at cs dot ucla.edu
2020-12-21  7:15 ` eggert at cs dot ucla.edu
2020-12-23  5:28 ` eggert at cs dot ucla.edu
2020-12-24  0:28 ` eggert at cs dot ucla.edu
2020-12-29  8:47 ` eggert at cs dot ucla.edu
2023-12-29 11:10 ` gabravier at gmail dot com

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=bug-17924-131-iOSCwJiwr4@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).