The return of threading errors in ogg123

Peter Wemm peter at
Tue Feb 17 11:29:53 PST 2004

On Tuesday 17 February 2004 01:33 am, Adriaan de Groot wrote:
> 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/
> #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.

I'm currently suspicious of the implementation of signal delivery and 
return handling for unrelated reasons.  It is possible that its also 
affecting this.  I'm trying to diagnose/fix an i386 binary problem and 
it looks like something might be missing in the MD code thats needed 
for interaction with KSE, or something could be wrong with the ERESTART 
handling.  Anyway, I'll look into this again.

BTW; can somebody point me to a .ogg file I can test with?  

BTW2: the last time I asked for a .ogg file, I got sent a livejournal 
recording from one of the committers' sisters..  it was very scary. :-)
Peter Wemm - peter at; peter at; peter at
"All of this is for nothing if we don't go to the stars" - JMS/B5

More information about the freebsd-amd64 mailing list