Date: Mon, 03 May 2021 16:09:13 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 254995] pthread_cond_timedwait() returns EDEADLK Message-ID: <bug-254995-13406-EZyFZqL5tF@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 #4 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to nkoch from comment #3) Of course I cannot exclude memory corruption, but both condvar and mutex lo= oks consistent. And mutex seems to be owned by the errored thread, so the most likely cause is that mutex was not unlocked properly before sleeping for condvar. I read the code and do not see how could it happen. The only possible case which might cause some disturbance there is stop. Hm, could it be that some of y= our exec's failed? Do you ever exec from mt process, or only exec after fork? --=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-EZyFZqL5tF>