s390 - __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
- To: Matthias Klose <doko@cs.tu-berlin.de>
- Cc: Adam C Powell IV <hazelsct@debian.org>, debian-java@lists.debian.org, debian-s390@lists.debian.org, submit@bugs.debian.org
- Subject: libc6/s390 - __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
- From: Bastian Blank <waldi@debian.org>
- Date: Wed, 7 May 2008 11:29:49 +0200
- Message-id: <[🔎] 20080507092949.GA6006@wavehammer.waldi.eu.org>
- Mail-followup-to: Matthias Klose <doko@cs.tu-berlin.de>, Adam C Powell IV <hazelsct@debian.org>, debian-java@lists.debian.org, debian-s390@lists.debian.org, submit@bugs.debian.org
- In-reply-to: <[🔎] 18465.23412.132972.424279@gargle.gargle.HOWL>
- References: <[🔎] 1209997421.15917.81.camel@ozymandias.home.net> <[🔎] 20080505145852.GH20825@quadriga.konqueror.de> <[🔎] 1210004591.15917.108.camel@ozymandias.home.net> <[🔎] 18465.23412.132972.424279@gargle.gargle.HOWL>
Package: libc6 Version: 2.7-10 Severity: important On Wed, May 07, 2008 at 09:34:12AM +0200, Matthias Klose wrote: > the build failure on s390 is unexpected; is it possible to extract a > test case? | java: pthread_mutex_lock.c:71: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. So another package failed about that (after mono and libto$bla). It looks like a race condition somewhere in the libpthread. Bastian -- The more complex the mind, the greater the need for the simplicity of play. -- Kirk, "Shore Leave", stardate 3025.8
Reply to:
- Follow-Ups:
- Re: Bug#479952: libc6/s390 - __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
- From: Aurelien Jarno <aurelien@aurel32.net>
- Re: Bug#479952: libc6/s390 - __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
- References:
- Proper way to specify Java build-dep
- From: Adam C Powell IV <hazelsct@debian.org>
- Re: Proper way to specify Java build-dep
- From: Michael Koch <konqueror@gmx.de>
- Re: Proper way to specify Java build-dep
- From: Adam C Powell IV <hazelsct@debian.org>
- Re: Proper way to specify Java build-dep
- From: Matthias Klose <doko@cs.tu-berlin.de>
- Proper way to specify Java build-dep
- Prev by Date: Re: Proper way to specify Java build-dep
- Next by Date: java-common 0.30 MIGRATED to testing
- Previous by thread: Re: Proper way to specify Java build-dep
- Next by thread: Re: Bug#479952: libc6/s390 - __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
- Index(es):