This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/13724] pthread_setname_np segfault
- From: "yselkowitz at cygwin dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 23 Feb 2012 07:25:39 +0000
- Subject: [Bug nptl/13724] pthread_setname_np segfault
- Auto-submitted: auto-generated
- References: <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.