Date: Fri, 19 Apr 2019 14:27:05 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 237195] pthread_mutex_unlock crash as unlocked mutex destroyed by signaled thread Message-ID: <bug-237195-13406-HQCnsZVJuc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237195-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-237195-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=3D237195 --- Comment #8 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to freebsd from comment #5) It sounds like an access to the freed memory. Anyway, it is somewhat labor-intensive to read disassembly to track your is= sue, and since you did not disassemble the whole functions bodies, it is impossi= ble. Compile libc/libthr/rtld with debugging enabled: make -C lib/libc DEBUG_FLAGS=3D-g all install same for lib/libthr, libexec/rtld-elf. Then reproduce the issue and show the backtrace with debugging symbols, so that the source line numbers are easily seen. --=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-237195-13406-HQCnsZVJuc>