Date: Wed, 30 Sep 2009 22:27:09 -0500 From: Matt <datahead4@gmail.com> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: FreeBSD GNOME Users <freebsd-gnome@freebsd.org> Subject: Re: pthread_mutexattr_settype assertion from PulseAudio with Amarok 2.2 Message-ID: <cd6b4a5b0909302027ra4bf91fk6734c8b433ad3bf2@mail.gmail.com> In-Reply-To: <1254350826.94567.41.camel@shumai.marcuscom.com> References: <cd6b4a5b0909301459w7125e330k106673bfa93e97fa@mail.gmail.com> <1254350826.94567.41.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 30, 2009 at 5:47 PM, Joe Marcus Clarke <marcus@marcuscom.com> w= rote: > On Wed, 2009-09-30 at 16:59 -0500, Matt wrote: >> Does anyone know if the root cause of the "Assertion >> =E2=80=98pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE) =3D= =3D 0=E2=80=B2 >> failed at pulsecore/mutex-posix.c:52, function pa_mutex_new(). >> Aborting." error discussed at: >> >> http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/ >> >> was ever determined? =C2=A0I'm seeing this same error when trying to upd= ate >> the amarok-kde4 port to version 2.2 and the only discussion I can find >> related to this issue is at >> http://lists.freebsd.org/pipermail/freebsd-gnome/2009-July/022732.html >> and I don't see a resolution. >> >> Relevant data about my system: >> - All ports built in Tinderbox with "WITH_DEBUG=3Dyes" set >> - Tinderbox jail is 8-STABLE from 2009-09-10 16:42:33 >> - Tinderbox ports were updated 2009-09-14 12:59:10 >> - System where ports are installed is same host running the Tinderbox. >> =C2=A0"uname -a" states (sanitized) "FreeBSD <hostname> 8.0-RC1 FreeBSD >> 8.0-RC1 #0: Mon Sep 21 09:46:16 CDT 2009 >> root@<hostname>:/usr/obj/usr/src/sys/CUSTOM =C2=A0i386" >> - pkg_info list available at http://freebsd-gnome.pastebin.com/m1b0d9c9f >> >> I can't seem to get any usable core dumps from the system, but I can >> provide ktrace or other output if anyone is interested. > > I think there is a bug in the pthread_stubs in libc. =C2=A0If you apply t= his > patch, then rebuild libc, does the problem go away: > > http://www.marcuscom.com/downloads/_pthread_stubs.c.diff Yes, this eliminates the error mentioned above. Another patch to Amarok mentioned at: http://mail.kde.org/pipermail/amarok/2009-October/009340.html cleans up the rest of the problems I've been seeing. Thank you! Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd6b4a5b0909302027ra4bf91fk6734c8b433ad3bf2>