From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Make make-target-delegates grok namespace scope op and template params
Date: Mon, 30 Oct 2017 16:02:00 -0000 [thread overview]
Message-ID: <6d65bbfce86476451463c8d880c38a54@polymtl.ca> (raw)
In-Reply-To: <1509377531-21044-2-git-send-email-palves@redhat.com>
On 2017-10-30 11:32, Pedro Alves wrote:
> The next patch will want to use gdb::array_view<int> as parameter type
> of a target_ops method. However, that runs into a
> make-target-delegates limitation: target_debug_foo calls in
> target-delegates.c for parameters/return types with namespace scope
> operators ("::") or template parameters, end up looking like:
>
> @@ -1313,9 +1313,7 @@ debug_set_syscall_catchpoint (struct target_ops
> *self, int arg1, int arg2, int a
> fputs_unfiltered (", ", gdb_stdlog);
> target_debug_print_int (arg3);
> fputs_unfiltered (", ", gdb_stdlog);
> - target_debug_print_int (arg4);
> - fputs_unfiltered (", ", gdb_stdlog);
> - target_debug_print_int_p (arg5);
> + target_debug_print_gdb::array_view<const_int> (arg4);
>
> which obviously isn't something that compiles. The problem is that
> make-target-delegates wasn't ever taught that '::', '<', and '>' can
> appear in parameter/return types. You could work around it by hidding
> the unsupported characters behind a typedef in the target method
> declaration, or by using an explicit TARGET_DEBUG_PRINTER, but it's
> better to just remove the limitation.
>
> While at it, also fix an "abuse" of reserved identifiers.
>
> gdb/ChangeLog:
> yyyy-mm-dd Pedro Alves <palves@redhat.com>
>
> * make-target-delegates (munge_type): Also munge '<', '>', and
> ':'. Avoid double underscores in identifiers, and trailing
> underscores.
> * target-debug.h
> (target_debug_print_VEC_static_tracepoint_marker_p__p): Rename to
> ...
> (target_debug_print_VEC_static_tracepoint_marker_p_p): ... this.
> * target-delegates.c: Regenerate.
> ---
> gdb/make-target-delegates | 12 +++++++++++-
> gdb/target-debug.h | 2 +-
> gdb/target-delegates.c | 2 +-
> 3 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/gdb/make-target-delegates b/gdb/make-target-delegates
> index fd51c64..1773232 100755
> --- a/gdb/make-target-delegates
> +++ b/gdb/make-target-delegates
> @@ -232,8 +232,18 @@ sub munge_type($) {
> $result = $1;
> } else {
> ($result = $typename) =~ s/\s+$//;
> - $result =~ s/[ ()]/_/g;
> + $result =~ s/[ ()<>:]/_/g;
> $result =~ s/[*]/p/g;
> +
> + # Identifers with double underscores are reserved to the C++
> + # implementation.
> + $result =~ s/_+/_/g;
> +
> + # Avoid ending the function name with underscore, for
> + # cosmetics. Trailing underscores appear after munging types
> + # with template parameters, like e.g. "foo<int>".
> + $result =~ s/_$//g;
> +
> $result = 'target_debug_print_' . $result;
> }
>
> diff --git a/gdb/target-debug.h b/gdb/target-debug.h
> index 14196b4..068495e 100644
> --- a/gdb/target-debug.h
> +++ b/gdb/target-debug.h
> @@ -116,7 +116,7 @@
> target_debug_do_print (host_address_to_string (X))
> #define target_debug_print_mem_region_vector(X) \
> target_debug_do_print (host_address_to_string (X.data ()))
> -#define target_debug_print_VEC_static_tracepoint_marker_p__p(X) \
> +#define target_debug_print_VEC_static_tracepoint_marker_p_p(X) \
> target_debug_do_print (host_address_to_string (X))
> #define target_debug_print_const_struct_target_desc_p(X) \
> target_debug_do_print (host_address_to_string (X))
> diff --git a/gdb/target-delegates.c b/gdb/target-delegates.c
> index e0d7a9a..1cbe6f8 100644
> --- a/gdb/target-delegates.c
> +++ b/gdb/target-delegates.c
> @@ -3352,7 +3352,7 @@ debug_static_tracepoint_markers_by_strid (struct
> target_ops *self, const char *a
> fputs_unfiltered (", ", gdb_stdlog);
> target_debug_print_const_char_p (arg1);
> fputs_unfiltered (") = ", gdb_stdlog);
> - target_debug_print_VEC_static_tracepoint_marker_p__p (result);
> + target_debug_print_VEC_static_tracepoint_marker_p_p (result);
> fputs_unfiltered ("\n", gdb_stdlog);
> return result;
> }
LGTM, I'll make a patch to remove the mem_region_vector typedef.
Simon
next prev parent reply other threads:[~2017-10-30 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 15:32 [PATCH 0/2] Make make-target-delegates grok C++ type names better Pedro Alves
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 ` 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:59 ` 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 [this message]
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=6d65bbfce86476451463c8d880c38a54@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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