From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15313 invoked by alias); 26 Dec 2016 14:17:53 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 15274 invoked by uid 89); 26 Dec 2016 14:17:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=downloaded, Hx-languages-length:1952, owner's, omgalvan86gmailcom X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-yw0-f194.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OUmYEiQ2CZj29n3HBz/6/kVem7yXU1NoQrCL5nKAkqA=; b=Zs78uvxu2HrURH7xSgAmIBqCte6WmeSgvquPiR9HVGsGFoD6RTG3S1U89Nx+peqN2f XYBAsvoy7L0JgNiIENf7p7EPH3h9pvno7WV2YTiYnlijfcGeKR/ZkTnz5G3iYQdJZH0N bkA8Lr4C1/rhVPK1hoVRU+VLvnI8ZXRJlY//FwQIO4NC8p5R7xYCz/NcbZXUAwm/+ftq WX0Xd9ztzCF8kwCiKTQ5eeB9g/ORl1Dofs+rWVAokhvIaTH16BA7q/k5u+kZsOl+jHP9 3Q9QfrGW/Dze8nHXeunTKpqFTAch/3+09mwnUkvk9W1F1sCdGTiumtb1+h9L9Q/8ka+d MfXQ== X-Gm-Message-State: AIkVDXLFjcZQORyZ79FMKOshpowBON4exhLoUymTxUd0MKHJ0nTf3uIFjtIpSccVbUsjO0kiGHyNo5kkNaGS+Q== X-Received: by 10.13.219.82 with SMTP id d79mr21889265ywe.107.1482761860504; Mon, 26 Dec 2016 06:17:40 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1481576088-15304-1-git-send-email-omgalvan.86@gmail.com> <1482424494.14990.810.camel@redhat.com> <1482447010.14990.815.camel@redhat.com> <1482512736.14990.831.camel@redhat.com> <1482518873.14990.832.camel@redhat.com> From: Martin Galvan Date: Mon, 26 Dec 2016 14:17:00 -0000 Message-ID: Subject: Re: [PATCH v11] Add pretty printers for the NPTL lock types To: Torvald Riegel Cc: siddhesh@sourceware.org, Joseph Myers , libc-alpha@sourceware.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2016-12/txt/msg00956.txt.bz2 2016-12-23 16:37 GMT-03:00 Martin Galvan : > 2016-12-23 15:47 GMT-03:00 Torvald Riegel : >> Status = Locked, possibly with no waiters, Owner ID = 0, Robust = No, > > That's odd, IIRC locked mutexes always record their owner's ID. I > assume manually printing mutex->__data.__owner at that point shows 0 > too, right? I've done some more testing and still can't reproduce the error. I've tried using gdb 7.12 (sources downloaded from the GNU FTP site) and Python 2.7.5 on Ubuntu 16.04, x86_64. gdb -configure shows: This GDB was configured as follows: configure --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-auto-load-dir=$debugdir:$datadir/auto-load --with-auto-load-safe-path=$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=/home/martin/Documents/gdb-7.12/install/share/gdb (relocatable) --with-jit-reader-dir=/home/martin/Documents/gdb-7.12/install/lib/gdb (relocatable) --without-libunwind-ia64 --without-lzma --with-python=/home/martin/Documents/python-2.7.5/install --without-guile --with-separate-debug-dir=/home/martin/Documents/gdb-7.12/install/lib/debug (relocatable) --without-babeltrace I set LD_LIBRARY_PATH to the Python 2.7.5 lib install path so that gdb would pick the correct libpython2.7.so. I can post the output of gdb's python's sysconfig.get_config_vars(), though it's quite verbose. In any case, manually running gdb and stepping through the target until line 80 (after locking the non-robust mutex, which is where I'm assuming the test fails) still shows mutex->__data.__owner as being the owner's TID. Perhaps it would be useful to see what the mutex's member values are in your case. At one point I thought your mutex might've been showing all zeroes, but at least __data.__lock must be non-zero for it to show as locked. Any other info that could help me reproduce the error is welcome.