From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: wanghanlin@corp.netease.com
Cc: libc-help@sourceware.org, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: __pthread_mutex_lock assertion error with a simple test program
Date: Thu, 20 Feb 2020 09:02:00 -0000 [thread overview]
Message-ID: <CAH6eHdSD9F7Db=UKh=q3aQAaqHiUn58EJJCj9yp9bUnUCrWD5A@mail.gmail.com> (raw)
In-Reply-To: <72ad57af.1380.17060da4702.Coremail.wanghanlin@corp.netease.com>
On Thu, 20 Feb 2020 at 04:28, <wanghanlin@corp.netease.com> wrote:
>
> Dear All,
> Recently on my X86 server one problem hit.
> ../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
> The test program of appendix [1] is very simple.
> Strangely, there are hundreds of identical servers, but only two have this problem.
It doesn't look like a GCC problem though.
next prev parent reply other threads:[~2020-02-20 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 4:28 wanghanlin
2020-02-20 5:07 ` Paul Pluzhnikov via libc-help
2020-02-20 9:02 ` Jonathan Wakely [this message]
2021-09-27 14:35 libc-help&sourceware org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdSD9F7Db=UKh=q3aQAaqHiUn58EJJCj9yp9bUnUCrWD5A@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=libc-help@sourceware.org \
--cc=wanghanlin@corp.netease.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).