Date: Fri, 20 Aug 2021 08:37:56 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 254995] pthread_cond_timedwait() returns EDEADLK Message-ID: <bug-254995-13406-xdcmvMkIaE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254995-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-254995-13406@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=3D254995 --- Comment #8 from nkoch@demig.de --- As a temporary workaround I changed my code to handle EDEADLK from pthread_cond_timedwait() like ETIMEDOUT. Now I've got a runtime exception from within libthr: Fatal error 'mutex 0x6531800 own 0x1871e is not on list 0x0 0x0' at line 14= 1 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno =3D 0) This comes from a different cond/mutex pair when calling pthread_mutex_unlo= ck() after a pthread_cond_timedwait(). #0 0x0613058b in thr_kill () from /lib/libc.so.7 #1 0x0612ea8b in raise () from /lib/libc.so.7 #2 0x060ad0cf in abort () from /lib/libc.so.7 #3 0x05fbfb0d in ?? () from /lib/libthr.so.3 #4 0x05fb9fb4 in ?? () from /lib/libthr.so.3 #5 0x05fb9a9e in ?? () from /lib/libthr.so.3 #6 0x05fb9993 in pthread_mutex_unlock () from /lib/libthr.so.3 --=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-254995-13406-xdcmvMkIaE>