public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18641] New: pwd.h: add __nonnull markings
Date: Wed, 08 Jul 2015 07:16:00 -0000 [thread overview]
Message-ID: <bug-18641-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18641
Bug ID: 18641
Summary: pwd.h: add __nonnull markings
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: vapier at gentoo dot org
CC: drepper.fsp at gmail dot com
Target Milestone: ---
per the thread:
https://sourceware.org/ml/libc-alpha/2015-05/msg00867.html
when you use many functions in pwd.h with NULL pointers, glibc will crash.
POSIX doesn't require NULL to be supported, so we want to mark all the funcs as
nonnull instead. this way user code is compiled with warnings and our API
expectations are documented.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-07-08 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 7:16 vapier at gentoo dot org [this message]
2015-07-08 7:22 ` [Bug libc/18641] " cvs-commit at gcc dot gnu.org
2015-07-08 7:22 ` vapier at gentoo dot org
2015-07-24 14:44 ` fweimer at redhat dot com
2015-07-28 3:41 ` vapier at gentoo dot org
2015-07-28 3:47 ` cvs-commit at gcc dot gnu.org
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-18641-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).