public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Paul Pluzhnikov via libc-help" <libc-help@sourceware.org>
To: wanghanlin@corp.netease.com
Cc: libc-help <libc-help@sourceware.org>, gcc-help@gcc.gnu.org
Subject: Re: __pthread_mutex_lock assertion error with a simple test program
Date: Thu, 20 Feb 2020 05:07:00 -0000	[thread overview]
Message-ID: <CALoOobP0H88XJpczbubVc9Y7uqx0vsc7_vU44cPtoCZ6vWUhQQ@mail.gmail.com> (raw)
In-Reply-To: <72ad57af.1380.17060da4702.Coremail.wanghanlin@corp.netease.com>

On Wed, Feb 19, 2020 at 8:28 PM <wanghanlin@corp.netease.com> wrote:

>
> Strangely, there are hundreds of identical servers, but only two have this
> problem.
>

Have you ruled out the possibility that these two servers have faulty CPU
or memory?

-- 
Paul Pluzhnikov

  reply	other threads:[~2020-02-20  5:07 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 [this message]
2020-02-20  9:02 ` Jonathan Wakely
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=CALoOobP0H88XJpczbubVc9Y7uqx0vsc7_vU44cPtoCZ6vWUhQQ@mail.gmail.com \
    --to=libc-help@sourceware.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ppluzhnikov@google.com \
    --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).