public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yselkowitz at cygwin dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/13724] pthread_setname_np segfault
Date: Thu, 23 Feb 2012 07:26:00 -0000 [thread overview]
Message-ID: <bug-13724-131-Vzg2UalCxH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13724-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13724
--- Comment #3 from Cygwin/X maintainer <yselkowitz at cygwin dot com> 2012-02-23 07:25:39 UTC ---
(In reply to comment #2)
> When it isn't documented in man pages or info pages, the headers are the only
> documentation. And the headers clearly document that you must not call it with
> NULL:
I understand that, but that doesn't necessarily mean it should segfault if NULL
is passed anyway. pthread_getname_np(thr, NULL, 16) returns EFAULT, but
pthread_setname_np(thr, NULL) segfaults. That inconsistency in a corresponding
pair of functions seems odd to me, hence the question if this is the intended
result.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-23 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 19:06 [Bug nptl/13724] New: " law at redhat dot com
2012-02-23 1:32 ` [Bug nptl/13724] " yselkowitz at cygwin dot com
2012-02-23 3:05 ` yselkowitz at cygwin dot com
2012-02-23 7:11 ` jakub at redhat dot com
2012-02-23 7:26 ` yselkowitz at cygwin dot com [this message]
2012-02-23 10:02 ` schwab@linux-m68k.org
2013-10-08 14:56 ` neleai at seznam dot cz
2014-06-26 15:20 ` fweimer at redhat 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-13724-131-Vzg2UalCxH@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).