Date: Thu, 19 Oct 2006 21:26:55 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Mikhail Teterin" <mi+mx@aldan.algebra.com> Cc: gnome@freebsd.org, threads@freebsd.org Subject: Re: devel/nspr's self-test failing: `mutex is on list' Message-ID: <op.tho7q5dx9aq2h7@mezz.mezzweb.com> In-Reply-To: <200610192217.17383.mi%2Bmx@aldan.algebra.com> References: <200610192217.17383.mi%2Bmx@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Oct 2006 21:17:16 -0500, Mikhail Teterin = <mi+mx@aldan.algebra.com> wrote: > Unfortunately, the tests are not being run automatically every time th= e = > port > builds, so we don't know, when the problem began... > > To reproduce: > > % cd /usr/ports/devel/nspr > % make build test > > [...] > forktest FAILED > forktest: Wait one second before accept > forktest: Wait one second before connect > forktest: Connecting to port 51686 > forktest: Writing message "Hello world!" > forktest: Accepting connection at port 51686 > forktest: Received "Hello world!" from the client > forktest: The message is received correctly > forktest: Fork succeeded. Parent process continues. > forktest: Wait one second before accept > forktest: Wait one second before connect > forktest: Fatal error 'mutex is on list' at line 540 in = = > file /usr/src/lib/libpthread/thread/thr_mutex.c (errno =3D 43) > forktest: Fork succeeded. Child process continues. > forktest: Accepting connection at port 56714 > forktest: Connecting to port 56714 > forktest: Writing message "Hello world!" > forktest: Received "Hello world!" from the client > forktest: The message is received correctly > forktest: Parent process exits. > forktest: FAILED > [...] > > I'm unsure, whether the bug is in the test itself or in the pthread, > or in the nspr-library's threading implementation, but the test used > to pass... > > Would a thread-expert care to investigate, please? Thanks! It's known and there has a PR (ports/100785) for it with no solution. I = = have a backtrace that forktest dumped a core if you know how to dig in a= nd = solve it. http://people.freebsd.org/~mezz/gdb/gdb-nspr-forktest.txt marcus said, 'Looks like a potential symbol conflict, but without full = libpthread and libc symbols, it's hard to tell.' I have have done compil= ed = these with the debug but I haven't hear anything so far. Cheers, Mezz > -mi -- = mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.tho7q5dx9aq2h7>