From: Pedro Alves <palves@redhat.com>
To: James Hogan <james.hogan@imgtec.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] MIPS: Ignore invalid regs during info registers all
Date: Tue, 30 Sep 2014 15:01:00 -0000 [thread overview]
Message-ID: <542AC5A9.7060101@redhat.com> (raw)
In-Reply-To: <1412088186-26402-1-git-send-email-james.hogan@imgtec.com>
On 09/30/2014 03:43 PM, James Hogan wrote:
> The "info registers all" command causes mips_print_registers_info () to be
> called for all register numbers, including invalid ones such as unused DSP
> register numbers. This triggers an error () call which prevents further
> register values being printed. Just silently return without printing
> anything or erroring, so that all valid registers can be printed.
What happens when the user does "info registers that-unused-register" ?
Thanks,
Pedro Alves
>
> For example, before this patch:
> (gdb) info registers all
> zero: 0x0
> ...
> fir: 0x30f30320
> Not a valid register for the current processor type
> (gdb)
>
> After this patch:
> (gdb) info registers all
> zero: 0x0
> ...
> fir: 0x30f30320
> restart: 0x0
> (gdb)
>
> gdb/ChangeLog:
>
> * mips-tdep.c (mips_print_registers_info): Replace error for
> single invalid register with silent return.
> ---
> gdb/ChangeLog | 5 +++++
> gdb/mips-tdep.c | 2 +-
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index f3282144c303..5da8415c3ca0 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,3 +1,8 @@
> +2014-09-30 James Hogan <james.hogan@imgtec.com>
> +
> + * mips-tdep.c (mips_print_registers_info): Replace error for
> + single invalid register with silent return.
> +
> 2014-09-30 Andreas Arnez <arnez@linux.vnet.ibm.com>
>
> * gdbarch.sh (regset_from_core_section): Remove gdbarch method.
> diff --git a/gdb/mips-tdep.c b/gdb/mips-tdep.c
> index 188580f2ebdc..3c4665457552 100644
> --- a/gdb/mips-tdep.c
> +++ b/gdb/mips-tdep.c
> @@ -6332,7 +6332,7 @@ mips_print_registers_info (struct gdbarch *gdbarch, struct ui_file *file,
> {
> gdb_assert (regnum >= gdbarch_num_regs (gdbarch));
> if (*(gdbarch_register_name (gdbarch, regnum)) == '\0')
> - error (_("Not a valid register for the current processor type"));
> + return;
>
> mips_print_register (file, frame, regnum);
> fprintf_filtered (file, "\n");
>
next prev parent reply other threads:[~2014-09-30 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 14:43 James Hogan
2014-09-30 15:01 ` Pedro Alves [this message]
2014-09-30 15:05 ` James Hogan
2014-09-30 15:36 ` Pedro Alves
2014-10-03 16:32 ` Maciej W. Rozycki
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=542AC5A9.7060101@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=james.hogan@imgtec.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