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

Might be unrelated, this is a stack-trace of a different test:

http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/test/X/ags_functional_machine_add_and_destroy_test.c?h=0.7.122.x

Here is  WindowMaker unresponsive. No more input possible until the
test was killed.
It is a data-race since it doesn't happen all the time.

Bests,
Joël


On Wed, Mar 15, 2017 at 7:31 PM, Joël Krähemann <jkraehemann@gmail.com> wrote:
> Hi
>
> 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.
>
> Cheers,
> Joël

Attachment: log
Description: Binary data


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