public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: <libc-alpha@sourceware.org>, <gdb@sourceware.org>,
	Daniel Walker <danielwa@cisco.com>
Subject: Re: [PATCH v2 0/2] Extend struct r_debug to support multiple namespaces
Date: Tue, 17 Aug 2021 17:57:12 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2108171754450.208325@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20210817010629.593479-1-hjl.tools@gmail.com>

On Mon, 16 Aug 2021, H.J. Lu via Gdb wrote:

> 1. Bump r_version to 2.  This triggers the GDB bug:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=28236

This seems like it needs a NEWS entry under "Deprecated and removed 
features, and other changes affecting compatibility" if it results in a 
user-visible problem using older GDB with newer glibc (that bug report 
doesn't say what the actual user-visible symptoms are, if any).  (The new 
feature should probably have a NEWS entry under "Major new features" in 
any case.)

-- 
Joseph S. Myers
joseph@codesourcery.com

      parent reply	other threads:[~2021-08-17 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  1:06 H.J. Lu
2021-08-17  1:06 ` [PATCH v2 1/2] Add declare_object_symbol_alias for assembly codes [BZ #28128] H.J. Lu
2021-08-17  1:06 ` [PATCH v2 2/2] Extend struct r_debug to support multiple namespaces H.J. Lu
2021-08-17 17:44   ` Daniel Walker
2021-08-17 20:25     ` H.J. Lu
2021-08-18  0:14       ` H.J. Lu
2021-08-17 17:57   ` Daniel Walker
2021-08-17 20:26     ` H.J. Lu
2021-08-18  0:21       ` H.J. Lu
2021-08-18  2:36         ` H.J. Lu
2021-08-18 13:34           ` H.J. Lu
2021-08-17 17:57 ` Joseph Myers [this message]

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.22.394.2108171754450.208325@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=danielwa@cisco.com \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    /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).