From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] Remove C++ Symbol Aliases From Completion List
Date: Fri, 27 Dec 2019 21:32:00 -0000 [thread overview]
Message-ID: <cover.1577481992.git.andrew.burgess@embecosm.com> (raw)
Read patch #2 to understand what the motivation for this series is.
Patch #1 is setup work.
---
Andrew Burgess (2):
gdb: Convert completion tracker to use std types
gdb: Remove C++ symbol aliases from completion list
gdb/ChangeLog | 35 ++++++
gdb/completer.c | 138 ++++++++++++---------
gdb/completer.h | 62 ++++++---
gdb/symtab.c | 18 +++
gdb/testsuite/ChangeLog | 5 +
.../gdb.linespec/cp-completion-aliases.cc | 73 +++++++++++
.../gdb.linespec/cp-completion-aliases.exp | 57 +++++++++
7 files changed, 313 insertions(+), 75 deletions(-)
create mode 100644 gdb/testsuite/gdb.linespec/cp-completion-aliases.cc
create mode 100644 gdb/testsuite/gdb.linespec/cp-completion-aliases.exp
--
2.14.5
next prev reply other threads:[~2019-12-27 21:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 0:37 [PATCHv2 0/3] " Andrew Burgess
2019-12-27 21:32 ` Andrew Burgess [this message]
2019-12-27 21:32 ` [PATCH 2/2] gdb: Remove C++ symbol aliases from completion list Andrew Burgess
2020-01-24 19:08 ` Tom Tromey
2019-12-27 21:32 ` [PATCH 1/2] gdb: Convert completion tracker to use std types Andrew Burgess
2020-01-24 19:18 ` Tom Tromey
2020-01-24 19:47 ` Christian Biesinger via gdb-patches
2020-01-26 16:01 ` Tom Tromey
2020-01-28 0:37 ` [PATCHv2 3/3] gdb: Remove C++ symbol aliases from completion list Andrew Burgess
2020-05-24 11:35 ` Pedro Alves
2020-05-24 12:34 ` [pushed] Don't remove C++ aliases from completions if symbol doesn't match (Re: [PATCHv2 3/3] gdb: Remove C++ symbol aliases from completion list) Pedro Alves
2020-05-25 14:34 ` GDB crash due to infinite recursion in typedef substitution " Pedro Alves
2020-05-26 17:02 ` Andrew Burgess
2020-05-26 18:09 ` Pedro Alves
2020-05-26 21:17 ` Keith Seitz
2020-05-27 19:36 ` Pedro Alves
2020-05-28 13:40 ` Pedro Alves
2020-01-28 0:37 ` [PATCHv2 2/3] gdb: Restructure the completion_tracker class Andrew Burgess
2020-04-03 23:00 ` Luis Machado
2020-04-04 15:37 ` [PATCH] gdb: Don't corrupt completions hash when expanding the hash table Andrew Burgess
2020-04-06 20:27 ` Tom Tromey
2020-04-15 15:46 ` Andrew Burgess
2020-01-28 0:50 ` [PATCHv2 1/3] libiberty/hashtab: More const parameters Andrew Burgess
2020-02-25 17:35 ` Andrew Burgess
2020-03-12 10:33 ` [PATCHv2 0/3] Remove C++ Symbol Aliases From Completion List Andrew Burgess
2020-03-12 19:17 ` Tom Tromey
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=cover.1577481992.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@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).