From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 2/8] Use counted_command_line everywhere
Date: Tue, 24 Apr 2018 16:43:00 -0000 [thread overview]
Message-ID: <ea99b3d5-3d82-c30f-1730-e05bf5f1a1b6@redhat.com> (raw)
In-Reply-To: <20180419191539.661-3-tom@tromey.com>
On 04/19/2018 08:15 PM, Tom Tromey wrote:
> Currently command lines are reference counted using shared_ptr only
> when attached to breakpoints. This patch changes gdb to use
> shared_ptr in commands as well. This allows for the removal of
> copy_command_lines.
>
> Note that the change to execute_user_command explicitly makes a new
> reference to the command line. This will be used in a later patch.
>
> This simplifies struct command_line based on the observation that a
> given command can have at most two child bodies: an "if" can have both
> "then" and "else" parts. Perhaps the names I've chosen for the
> replacements here are not very good -- your input requested.
>
Names look fine to me.
> @@ -2663,11 +2663,10 @@ trace_dump_actions (struct command_line *action,
>
> if (cmd_cfunc_eq (cmd, while_stepping_pseudocommand))
> {
> - int i;
> -
> - for (i = 0; i < action->body_count; ++i)
> - trace_dump_actions (action->body_list[i],
> - 1, stepping_frame, from_tty);
> + trace_dump_actions (action->body_list_0.get (),
> + 1, stepping_frame, from_tty);
> + trace_dump_actions (action->body_list_1.get (),
> + 1, stepping_frame, from_tty);
Hmm, this looked suspicious. I'm not seeing why would a
while-stepping action have two body lists. I guess this
happens to work because trace_dump_actions does nothing
if ACTION is NULL.
> @@ -2797,17 +2792,13 @@ all_tracepoint_actions_and_cleanup (struct breakpoint *t)
> if (*default_collect)
> {
> struct command_line *default_collect_action;
> - char *default_collect_line;
> -
> - default_collect_line = xstrprintf ("collect %s", default_collect);
> - make_cleanup (xfree, default_collect_line);
> + gdb::unique_xmalloc_ptr<char> default_collect_line
> + (xstrprintf ("collect %s", default_collect));
string_printf ?
>
> - validate_actionline (default_collect_line, t);
> - default_collect_action = XNEW (struct command_line);
> - make_cleanup (xfree, default_collect_action);
> - default_collect_action->next = actions;
> - default_collect_action->line = default_collect_line;
> - actions = default_collect_action;
> + validate_actionline (default_collect_line.get (), t);
> + actions.reset (new struct command_line (simple_control,
> + default_collect_line.release ()),
> + command_lines_deleter ());
> }
LGTM.
It's a shame that we can't use std::make_shared to avoid
the separate control block allocation.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-04-24 16:43 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 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 2/8] Use counted_command_line everywhere Tom Tromey
2018-04-24 16:43 ` Pedro Alves [this message]
2018-04-24 23:11 ` Tom Tromey
2018-04-24 23:18 ` Tom Tromey
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 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 6/8] Use function_view in cli-script.c Tom Tromey
2018-04-22 19:02 ` Pedro Alves
2018-04-24 23:38 ` 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 1/8] Allocate cmd_list_element with new 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=ea99b3d5-3d82-c30f-1730-e05bf5f1a1b6@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).