Date: Mon, 02 May 2016 04:11:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 209194] Seg fault with pthread_cond_signal() and pthread_cond_broadcast() Message-ID: <bug-209194-16@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209194 Bug ID: 209194 Summary: Seg fault with pthread_cond_signal() and pthread_cond_broadcast() Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: threads Assignee: freebsd-threads@FreeBSD.org Reporter: michael.cress@cress.us I have code that is Seg Faulting with the following (partial) stack trace: #0 0x281fa7cf in pthread_getspecific () from /lib/libthr.so.3 #1 0x28201597 in pthread_cond_signal () from /lib/libthr.so.3 One thread exclusively is pthread_cond_timedwait()'ing on an initialized pthread_cond_t variable. Signalling occurs from another thread using pthread_cond_signal()/_broadcast(). Does anyone have any ideas on why this = seg fault is occuring/why the pthread_getspecific() internal call is failing? --=20 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-209194-16>