Date: Tue, 17 Feb 2004 10:33:07 +0100 (MET) From: Adriaan de Groot <adridg@sci.kun.nl> To: freebsd-amd64@freebsd.org Subject: The return of threading errors in ogg123 Message-ID: <Pine.GSO.4.44.0402171025520.15647-100000@wn4.sci.kun.nl>
next in thread | raw e-mail | index | archive | help
Since a couple of weeks again, on -CURRENT, ogg123 has started bus erroring and segfaulting again, just like it was back in november before Peter's stack fixes. The "backtrace" is: (gdb) bt #0 0x0000000200f19320 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x0000000200f10d68 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x0000000200f0f0ed in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #3 0xd0d0d0d0d0d0d0d0 in ?? () so that's totally useless; I've just finished complete upgrade cycle with FreeBSD beans.ebn.kun.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Feb 16 08:12:04 CET 2004 root@beans.ebn.kun.nl:/usr/obj/mnt/sys/CURRENT/src/sys/GENERIC amd64 and done a portupgrade -acf, so things ought to be clean. The problem doesn't trigger as often or as easily as it used to - I'm trying libc_r now to see if that makes a difference, as well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.44.0402171025520.15647-100000>