public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/17924] New: 'free' should not set errno
Date: Wed, 04 Feb 2015 00:06:00 -0000 [thread overview]
Message-ID: <bug-17924-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17924
Bug ID: 17924
Summary: 'free' should not set errno
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: malloc
Assignee: unassigned at sourceware dot org
Reporter: eggert at gnu dot org
As mentioned in <http://austingroupbugs.net/view.php?id=385>, the next major
POSIX release will require 'free' to not set errno. Rich Felker points out
some scenarios when glibc 'free' might set errno; see
<https://sourceware.org/ml/libc-alpha/2015-02/msg00067.html>. These scenarios
should be investigated and fixed.
Also, the glibc documentation should be updated to make it clear to users that
glibc 'free' does not set errno, and that any replacements for 'free' should do
the same.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-02-04 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 0:06 eggert at gnu dot org [this message]
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
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@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).