From: Martin Galvan <omgalvan.86@gmail.com>
To: Torvald Riegel <triegel@redhat.com>
Cc: siddhesh@sourceware.org, Joseph Myers <joseph@codesourcery.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v11] Add pretty printers for the NPTL lock types
Date: Mon, 26 Dec 2016 14:17:00 -0000 [thread overview]
Message-ID: <CAN19L9FAH=FQMxvH5vhxF2EHhdUSkadORXLsGoaNJEbA=J7f+w@mail.gmail.com> (raw)
In-Reply-To: <CAN19L9E9FEjfmjaxiW-Mr4ueax-Raao+b_MJE6AMmWVN8T15eg@mail.gmail.com>
2016-12-23 16:37 GMT-03:00 Martin Galvan <omgalvan.86@gmail.com>:
> 2016-12-23 15:47 GMT-03:00 Torvald Riegel <triegel@redhat.com>:
>> 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.
next prev parent reply other threads:[~2016-12-26 14:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 3:04 Martin Galvan
2016-11-28 12:11 ` Stefan Liebler
2016-11-28 16:00 ` Martin Galvan
2016-12-04 12:41 ` Siddhesh Poyarekar
2016-12-04 20:56 ` Martin Galvan
2016-12-08 13:36 ` Siddhesh Poyarekar
2016-12-08 18:56 ` Joseph Myers
2016-12-08 21:01 ` Martin Galvan
2016-12-12 20:55 ` Martin Galvan
2016-12-12 23:15 ` Joseph Myers
2016-12-12 23:21 ` Martin Galvan
2016-12-14 18:20 ` Joseph Myers
2016-12-14 19:46 ` Martin Galvan
2016-12-17 18:10 ` Martin Galvan
2016-12-17 19:07 ` Siddhesh Poyarekar
2016-12-17 19:09 ` Martin Galvan
2016-12-22 16:35 ` Torvald Riegel
2016-12-22 16:44 ` Martin Galvan
2016-12-22 22:50 ` Torvald Riegel
2016-12-22 23:40 ` Martin Galvan
2016-12-23 17:05 ` Torvald Riegel
2016-12-23 17:40 ` Martin Galvan
2016-12-23 18:05 ` Martin Galvan
2016-12-23 18:48 ` Torvald Riegel
2016-12-23 19:38 ` Martin Galvan
2016-12-26 14:17 ` Martin Galvan [this message]
2017-01-02 12:48 ` Martin Galvan
2017-01-02 13:51 ` Joseph Myers
2017-01-02 14:35 ` Martin Galvan
2017-01-02 15:47 ` Torvald Riegel
2017-01-02 21:51 ` Joseph Myers
2017-01-03 7:27 ` Siddhesh Poyarekar
2017-01-06 21:58 ` Torvald Riegel
2017-01-09 19:37 ` Martin Galvan
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='CAN19L9FAH=FQMxvH5vhxF2EHhdUSkadORXLsGoaNJEbA=J7f+w@mail.gmail.com' \
--to=omgalvan.86@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@sourceware.org \
--cc=triegel@redhat.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).