From: Keith Seitz <keiths@redhat.com>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] replace_typedefs: handle templates in namespaces
Date: Thu, 28 May 2020 15:13:24 -0700 [thread overview]
Message-ID: <5964d724-852f-c5bf-7e96-af56c4dc2141@redhat.com> (raw)
In-Reply-To: <20200528133724.24634-2-palves@redhat.com>
On 5/28/20 6:37 AM, Pedro Alves via Gdb-patches wrote:
> gdb/ChangeLog:
> 2020-05-28 Pedro Alves <palves@redhat.com>
>
> * cp-support.c (replace_typedefs_template): New.
> (replace_typedefs_qualified_name): Handle
> DEMANGLE_COMPONENT_TEMPLATE.
>
> gdb/testsuite/ChangeLog:
> 2020-05-28 Pedro Alves <palves@redhat.com>
>
> * gdb.linespec/cp-replace-typedefs-ns-template.cc: New.
> * gdb.linespec/cp-replace-typedefs-ns-template.exp: New.
This is very close to where I was headed, so AFAICT, it LGTM.
Thanks a bunch for pursuing this while I've been tied up with other
tasks.
Keith
next prev parent reply other threads:[~2020-05-28 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 13:37 [PATCH 1/1] Fix GDB crash due to infinite recursion in typedef substitution Pedro Alves
2020-05-28 13:37 ` [PATCH 1/1] replace_typedefs: handle templates in namespaces Pedro Alves
2020-05-28 22:13 ` Keith Seitz [this message]
2020-05-30 15:34 ` Pedro Alves
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=5964d724-852f-c5bf-7e96-af56c4dc2141@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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).