Date: Fri, 18 Mar 2016 03:30:51 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: "Oleg V. Nauman" <oleg@opentransfer.com> Cc: freebsd-current@freebsd.org Subject: Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35) Message-ID: <20160318013051.GT1741@kib.kiev.ua> In-Reply-To: <5093647.qxI0C33PyG@asus.theweb.org.ua> References: <5093647.qxI0C33PyG@asus.theweb.org.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 17, 2016 at 09:40:11PM +0200, Oleg V. Nauman wrote: > > I'm experiencing issue with threaded applications ( including many KDE > applications ) after recent CURRENT update. Attempt to start application cause > Abort trap (6) with "Fatal error 'mutex is on list' at line 139 in file > /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)" output on console. > > FreeBSD 11.0-CURRENT amd64 r296887 > > Backtrace from application looks like > > Application: KGpg (kgpg), signal: Abort trap > [Switching to Thread 810815000 (LWP 100865/kgpg)] > [KCrash Handler] > #8 0x0000000807176d6a in thr_kill () from /lib/libc.so.7 > #9 0x0000000807176d3b in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:52 > #10 0x0000000807176ca9 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 > #11 0x0000000806e9e62c in _thread_exit (fname=<value optimized out>, > lineno=<value optimized out>, msg=<value optimized out>) at > /usr/src/lib/libthr/thread/thr_exit.c:182 > #12 0x0000000806e996fc in mutex_lock_common (m=<value optimized out>, > abstime=<value optimized out>, cvattach=<value optimized out>) at > /usr/src/lib/libthr/thread/thr_mutex.c:139 > #13 0x0000000806e98c20 in __pthread_mutex_timedlock (mutex=0x814600008, > abstime=0x7fffffff5a58) at /usr/src/lib/libthr/thread/thr_mutex.c:566 >From the frame 13, please do p *mutex p *m p **mutex What non-KDE apps exhibit the behaviour ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160318013051.GT1741>