From: Joseph Myers <joseph@codesourcery.com>
To: Martin Galvan <omgalvan.86@gmail.com>
Cc: Torvald Riegel <triegel@redhat.com>, <siddhesh@sourceware.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v11] Add pretty printers for the NPTL lock types
Date: Mon, 02 Jan 2017 13:51:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1701021347590.28945@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAN19L9FToOcGijtzptmZ=Wwk765+jkyx2-u6Uid4SRnpqDMdUQ@mail.gmail.com>
On Mon, 2 Jan 2017, Martin Galvan wrote:
> Guys, are there any news on this? Did the test fail for anyone else?
I'm seeing the following failures with current sources on x86_64. This is
with system GDB on Ubuntu 16.04 (but a locally built compiler, configured
as a cross compiler, for building glibc). System GDB is:
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
FAIL: nptl/test-cond-printers
FAIL: nptl/test-condattr-printers
FAIL: nptl/test-mutex-printers
FAIL: nptl/test-mutexattr-printers
FAIL: nptl/test-rwlock-printers
FAIL: nptl/test-rwlockattr-printers
test-cond-printers.out says:
Error: Response does not match the expected pattern.
Command: enable pretty-printer global glibc-pthread-locks
Expected pattern: [1-9][0-9]* of [1-9]+ printers enabled
Response: 0 printers enabled
0 of 1 printers enabled
(gdb)
and all the others are similar. GDB is linked with Python 3.5, which is
also the version found by configure.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-01-02 13:51 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
2017-01-02 12:48 ` Martin Galvan
2017-01-02 13:51 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1701021347590.28945@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=omgalvan.86@gmail.com \
--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).