public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Martin Galvan <martin.galvan@tallertechnologies.com>,
	libc-alpha@sourceware.org, carlos@redhat.com, palves@redhat.com,
	stli@linux.vnet.ibm.com
Subject: Re: [PATCH v11] Add pretty printers for the NPTL lock types
Date: Thu, 08 Dec 2016 13:36:00 -0000	[thread overview]
Message-ID: <a403327c-2635-4719-f33f-6c0f7f04237e@gotplt.org> (raw)
In-Reply-To: <85feaf1e-0445-e1ac-949b-6d33de849016@sourceware.org>

I have committed this now, with the NEWS block below.

Thank you for your patience and commitment!

Siddhesh


diff --git a/NEWS b/NEWS
index c2e973d..922a500 100644
--- a/NEWS
+++ b/NEWS
@@ -141,6 +141,11 @@ Version 2.25
   variable for a particular architecture in the GCC source file
   'gcc/config.gcc'.

+* GDB pretty printers have been added for mutex and condition variable
+  structures in POSIX Threads. When installed and loaded in gdb these
pretty
+  printers show various pthread variables in human-readable form when read
+  using the 'print' or 'display' commands in gdb.
+
 Security related changes:

   On ARM EABI (32-bit), generating a backtrace for execution contexts which

  parent reply	other threads:[~2016-12-08 13:36 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 [this message]
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
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=a403327c-2635-4719-f33f-6c0f7f04237e@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=martin.galvan@tallertechnologies.com \
    --cc=palves@redhat.com \
    --cc=siddhesh@sourceware.org \
    --cc=stli@linux.vnet.ibm.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).