AW: bug with PI mutex and static linking

[Warlich, Christof]

Carlos wrote:

> Works fine on Fedora 23 with glibc 2.22 and GCC 5.3.

Many thanks for that (rather unexpected) feedback. We also use GCC 5.3.

> You'll need to provide more information about your problem.

We are running Ubuntu 14.04 with self-built cross-toolchains for various architectures, amongst them x86_64.

Assuming you haven't missed to do a _static_ build to reproduce the issue, the problem seems to most
likely be with our toolchain build. So at least we now know where to start searching :-).

Cheers,

Chris

-----Ursprüngliche Nachricht-----
Von: Carlos O'Donell [mailto:carlos@systemhalted.org] 
Gesendet: Donnerstag, 11. Februar 2016 16:08
An: Warlich, Christof
Cc: libc-help@sourceware.org
Betreff: Re: bug with PI mutex and static linking

On Thu, Feb 11, 2016 at 5:03 AM, Warlich, Christof
<christof.warlich@siemens.com> wrote:
> with glibc 2.22, the following test fails on x86_64 when statically linking with EPERM when doing the pthread_mutex_unlock(). It looks like  mutex->__data.__owner is not properly initialized, as it is 0 when trying to unlock.

Works fine on Fedora 23 with glibc 2.22 and GCC 5.3.

You'll need to provide more information about your problem.

Cheers,
Carlos.