This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: dead-lock in glibc


Hi

Excuse me:

* WindowMaker 0.95.7-8
* debian unstable
* libc6 2.24-9
* MATE Terminal 1.16.1
* gcc (Debian 6.3.0-8) 6.3.0 20170221

Might be I was trying to do a recursive lock on a non-recursive mutex?
I was playing 64 beats with the notation editor of GSequencer in a infinite
loop. Suddenly it aborted after some playbacka approximetaly 3 to 4 minutes.

uptime
 21:34:24 up 1 day, 12:19,  1 user,  load average: 0.28, 0.39, 0.34

Bests,
Joël

On Wed, Mar 15, 2017 at 8:40 PM, Carlos O'Donell
<carlos@systemhalted.org> wrote:
> On Wed, Mar 15, 2017 at 2:31 PM, Joël Krähemann <jkraehemann@gmail.com> wrote:
>> I experience something strange:
>>
>> gsequencer: ../nptl/pthread_mutex_lock.c:349:
>> __pthread_mutex_lock_full: Assertion `INTERNAL_SYSCALL_ERRNO (e,
>> __err) != EDEADLK || (kind != PTHREAD_MUTEX_ERRORCHECK_NP && kind !=
>> PTHREAD_MUTEX_RECURSIVE_NP)' failed.
>> Aborted
>>
>> The window on XOrg is still present but the process doesn't exist anymore.
>
> What version of glibc? What distro?
>
> Cheers,
> Carlos.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]