From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 6/8] Use function_view in cli-script.c
Date: Sun, 22 Apr 2018 19:02:00 -0000 [thread overview]
Message-ID: <b13e452c-9539-8af4-c729-4a952d1ef0ab@redhat.com> (raw)
In-Reply-To: <20180419191539.661-7-tom@tromey.com>
On 04/19/2018 08:15 PM, Tom Tromey wrote:
> -/* The mi_read_next_line consults these variable to return successive
> - command lines. While it would be clearer to use a closure pointer,
> - it is not expected that any future code will use read_command_lines_1,
> - therefore no point of overengineering. */
Ahahahah :-)
> void
> mi_cmd_break_commands (const char *command, char **argv, int argc)
> {
> @@ -509,15 +492,24 @@ mi_cmd_break_commands (const char *command, char **argv, int argc)
> if (b == NULL)
> error (_("breakpoint %d not found."), bnum);
>
> - mi_command_line_array = argv;
> - mi_command_line_array_ptr = 1;
> - mi_command_line_array_cnt = argc;
> + int count = 1;
> + gdb::function_view<const char * ()> reader
> + = [&] ()
> + {
> + const char *result = nullptr;
> + if (count < argc)
> + result = argv[count++];
> + return result;
> + };
This is incorrect -- The 'reader' function_view is storing an address
to a closure whose lifetime ends right after the function_view ctor
is run. This a similar issue with assigning a string_view to
a temporary std::string, like:
std::string_view view = std::string ("temp");
C++ doesn't yet have a mechanism that allows making string_view and
types like it extend the lifetime of temporaries they're bound to,
like const references can.
You can fix the issue at hand here easily by not using function_view
at all:
auto reader = [&] ()
{
const char *result = nullptr;
if (count < argc)
result = argv[count++];
return result;
};
Now "reader" is the lambda closure itself.
> - cmd = read_command_lines (str.c_str (), from_tty, 1,
> - (is_tracepoint (b)
> - ? check_tracepoint_command : 0),
> - b);
> + gdb::function_view<void (const char *)> validator;
> + if (is_tracepoint (b))
> + validator = [=] (const char *line)
> + {
> + validate_actionline (line, b);
> + };
> +
> + cmd = read_command_lines (str.c_str (), from_tty, 1, validator);
> }
> }
Similar problem here. Something like this would fix it:
auto validator = [=] (const char *line)
{
validate_actionline (line, b);
};
decltype (callback) null_callback;
cmd = read_command_lines (str.c_str (), from_tty, 1,
is_tracepoint (b)
? validator : null_callback);
or use if/else:
if (is_tracepoint (b))
{
cmd = read_command_lines (str.c_str (), from_tty, 1,
[=] (const char *line)
{
validate_actionline (line, b);
};
}
else
cmd = read_command_lines (str.c_str (), from_tty, 1, nullptr);
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-04-22 19:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:16 [RFA 0/8] Various command-related improvements Tom Tromey
2018-04-19 19:16 ` [RFA 5/8] Allow defining a user command inside a user command Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-24 23:24 ` Tom Tromey
2018-04-19 19:16 ` [RFA 6/8] Use function_view in cli-script.c Tom Tromey
2018-04-22 19:02 ` Pedro Alves [this message]
2018-04-24 23:38 ` Tom Tromey
2018-04-19 19:16 ` [RFA 1/8] Allocate cmd_list_element with new Tom Tromey
2018-04-19 19:16 ` [RFA 7/8] Allow breakpoint commands to be set from Python Tom Tromey
2018-04-19 19:31 ` Eli Zaretskii
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 3/8] Make print_command_trace varargs Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 8/8] Let gdb.execute handle multi-line commands Tom Tromey
2018-04-19 19:32 ` Eli Zaretskii
2018-04-24 16:44 ` Pedro Alves
2018-04-19 19:16 ` [RFA 4/8] Constify prompt argument to read_command_lines Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 2/8] Use counted_command_line everywhere Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-24 23:11 ` Tom Tromey
2018-04-24 23:18 ` 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=b13e452c-9539-8af4-c729-4a952d1ef0ab@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).