From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Make make-target-delegates grok C++ type names better
Date: Mon, 30 Oct 2017 15:32:00 -0000 [thread overview]
Message-ID: <1509377531-21044-1-git-send-email-palves@redhat.com> (raw)
Using type names like std::string, std::vector<T> etc. in a target
method interface runs into a limitation in make-target-delegates. The
first patch in the series fixes that. I've wanted this before in my
multi-target series, and with C++-ification progressing, I guess
others will run into this too. Better just fix it.
The second patch makes use of that fix in code that I recently noticed
today could use gdb::array_view instead of a pointer+size pair, as an
example.
Pedro Alves (2):
Make make-target-delegates grok namespace scope op and template params
target_set_syscall_catchpoint, use gdb::array_view and bool
gdb/break-catch-syscall.c | 6 ++----
gdb/linux-nat.c | 4 ++--
gdb/make-target-delegates | 12 +++++++++++-
gdb/remote.c | 24 +++++++++++-------------
gdb/target-debug.h | 6 +++++-
gdb/target-delegates.c | 18 ++++++++----------
gdb/target.h | 23 ++++++++++-------------
7 files changed, 49 insertions(+), 44 deletions(-)
--
2.5.5
next reply other threads:[~2017-10-30 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 15:32 Pedro Alves [this message]
2017-10-30 15:32 ` [PATCH 2/2] target_set_syscall_catchpoint, use gdb::array_view and bool Pedro Alves
2017-10-30 15:59 ` Simon Marchi
2017-10-30 15:59 ` John Baldwin
2017-12-03 18:18 ` Simon Marchi
2017-12-06 22:38 ` John Baldwin
2017-12-06 22:50 ` Simon Marchi
2017-10-30 15:32 ` [PATCH 1/2] Make make-target-delegates grok namespace scope op and template params Pedro Alves
2017-10-30 16:02 ` Simon Marchi
2017-12-03 0:51 ` Simon Marchi
2017-12-03 11:58 ` Pedro Alves
2017-12-03 18:00 ` Simon Marchi
2017-10-30 17:05 ` [PATCH] Remove mem_region_vector typedef Simon Marchi
2017-12-03 18:06 ` Simon Marchi
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=1509377531-21044-1-git-send-email-palves@redhat.com \
--to=palves@redhat.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