From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: Add 'tui reg prev' command.
Date: Fri, 22 May 2015 17:06:00 -0000 [thread overview]
Message-ID: <555F61F7.9040809@redhat.com> (raw)
In-Reply-To: <20150522163739.GM2880@embecosm.com>
On 05/22/2015 05:37 PM, Andrew Burgess wrote:
> New version. I've addressed your comments from the first review. The
> reggroup_prev iterator has been fixed along the lines you suggested.
>
Great, thanks.
> +/* Implementation of the "tui reg prev" command. Cycle the register group
> + displayed in the tui REG window, moving backwards through the list of
> + available register groups. */
> +
> +static void
> +tui_reg_prev_command (char *arg, int from_tty)
> +{
> + struct gdbarch *gdbarch = get_current_arch ();
> +
> + if (TUI_DATA_WIN != NULL)
> + {
> + struct reggroup *group
> + = TUI_DATA_WIN->detail.data_display_info.current_group;
> +
> + group = reggroup_prev (gdbarch, group);
> + if (group == NULL)
> + group = reggroup_prev (gdbarch, NULL);
> +
> + if (group)
group != NULL.
> + tui_show_registers (group);
Indentation looks odd here.
Otherwise OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-05-22 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 22:17 [PATCH 0/2] Improvements to 'tui reg' command Andrew Burgess
2015-05-21 22:17 ` [PATCH 2/2] gdb: Rework command completion on 'tui reg' Andrew Burgess
2015-05-23 13:18 ` Pedro Alves
2015-06-02 10:11 ` Andrew Burgess
2015-06-02 15:01 ` Eli Zaretskii
2015-06-09 16:45 ` Pedro Alves
2015-05-21 22:17 ` [PATCH 1/2] gdb: Add 'tui reg prev' command Andrew Burgess
2015-05-22 1:06 ` Pedro Alves
2015-05-22 16:37 ` Andrew Burgess
2015-05-22 17:06 ` Pedro Alves [this message]
2015-05-22 7:15 ` Eli Zaretskii
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=555F61F7.9040809@redhat.com \
--to=palves@redhat.com \
--cc=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).