libc recently more aggressive about pthread locks in stable ?

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

I have just been debugging a ghostscript segfault on jessie amd64.

Looking at the code, I think that gs in jessie is plainly violating
the rules about the use of pthread locks.  On my partner's machine,
this makes it segfault on termination (with some input files, at
least).  On my machine it works just fine.  The code in sid is better.

I recently encountered what seems to be a similar bug in ogg123 in
stable.  #842796.

Has something changed in jessie's libc recently ?  I find it difficult
to imagine that these bugs would have been missed earlier during the
life of jessie.

I will try to make a patch to fix ghostscript, or at least file a
proper bug.  But, if there was a libc change, would it be possible to
revert it or make some kind of workaround ?

Thanks,
Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.