From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86150 invoked by alias); 20 Feb 2020 05:07:37 -0000 Mailing-List: contact libc-help-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: libc-help-owner@sourceware.org Received: (qmail 86119 invoked by uid 89); 20 Feb 2020 05:07:37 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-9.1 required=5.0 tests=AWL,BAYES_50,ENV_AND_HDR_SPF_MATCH,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy=ruled, sk:wanghan, wanghanlincorpneteasecom, hundreds X-HELO: mail-yb1-f174.google.com Received: from mail-yb1-f174.google.com (HELO mail-yb1-f174.google.com) (209.85.219.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 20 Feb 2020 05:07:35 +0000 Received: by mail-yb1-f174.google.com with SMTP id u47so621039ybi.1 for ; Wed, 19 Feb 2020 21:07:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jUCOVH0MUI3YbuOeT+orxH6v7WvalIve/Qd3WFJ48wA=; b=R4IneTswmxmB1xtl6XoY4vnAb85ZhES/Gm9OlCus/GMbZytKqlTQ+RD5s6ZKMpPy9E 4+uqZhDDvolBULOjBA+czA2AdiPMxH6qpoxspjVIJ9m0kx/rN57vy+ykGUMHjQl8/NiJ 9R61ZEDRNXkd0SaZ+gfe4lR/R7ZhXblFqvsu1ocxk+s2C4NTmQMuEN8u8/RVwPjXSbYq JU/GvJwW0qTGHXC4Wk+CLpQ7UqbK4jz/6spxFH8ULuN8blPT1md01DtGgCR5VOMEPoYb goUYSyzT33KgAr589RWtfXr4lP4VNYXHAhcrut9KM/6TyGJ2sCBYHv1q27rYZ+LeHFf5 3xqA== MIME-Version: 1.0 References: <72ad57af.1380.17060da4702.Coremail.wanghanlin@corp.netease.com> In-Reply-To: <72ad57af.1380.17060da4702.Coremail.wanghanlin@corp.netease.com> From: "Paul Pluzhnikov via libc-help" Reply-To: Paul Pluzhnikov Date: Thu, 20 Feb 2020 05:07:00 -0000 Message-ID: Subject: Re: __pthread_mutex_lock assertion error with a simple test program To: wanghanlin@corp.netease.com Cc: libc-help , gcc-help@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00020.txt.bz2 On Wed, Feb 19, 2020 at 8:28 PM 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