The return of threading errors in ogg123

Adriaan de Groot adridg at
Tue Feb 17 01:33:08 PST 2004

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
#1  0x0000000200f10d68 in pthread_mutexattr_init ()
   from /usr/lib/
#2  0x0000000200f0f0ed in pthread_mutexattr_init ()
   from /usr/lib/
#3  0xd0d0d0d0d0d0d0d0 in ?? ()

so that's totally useless; I've just finished complete upgrade cycle with

FreeBSD 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Feb 16
08:12:04 CET 2004
root at  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.

More information about the freebsd-amd64 mailing list