Date: Wed, 25 Oct 2017 07:52:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 223165] Crash with pthread_condattr_destroy(NULL) on freebsd-11 Message-ID: <bug-223165-16-lpAlSLjikz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223165-16@https.bugs.freebsd.org/bugzilla/> References: <bug-223165-16@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223165 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #2 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Conrad Meyer from comment #1) The SUSv7tc2 description of the function explicitely says that the behavior is undefined if the function is passed not a pointer to the previously initialized condattr object. So the internal acceptance of NULL does not really matter much there. Also, I am not sure why do you get SIGSEGV. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223165-16-lpAlSLjikz>