Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Kevin Buettner <kevinb@redhat.com>,
	Maciej W. Rozycki <macro@codesourcery.com>
Subject: [SH] regs command
Date: Wed, 16 May 2012 13:56:00 -0000	[thread overview]
Message-ID: <87ehqkrzzw.fsf@schwinge.name> (raw)

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

Hi!

There are issues with sh-tdep's regs command (»Print all registers«):

    (gdb) regs
          PC 295568c0       SR 00008000       PR 00000000     MACH 00000000
    Register 19 is not available

(After PC, SR, PR, MACH, this should print the values of the GBR, VBR
(this is register 19), MACL, then R0..R15.)  Evidently this code is not
prepared to cope with frame_unwind_register raising NOT_AVAILABLE_ERROR.

Now, the question is, why does the regs command exist at all?  It's been
present since the very first revision of sh-tdep.c, but as far as I can
tell, »info registers«/»info all-registers« can display all the register
information just fine, for example:

    (gdb) info all-registers
    r0             0x0      0
    [...]
    r15            0x7bab5c60       2074827872
    pc             0x295568c0       693463232
    pr             0x0      0
    gbr            0x29690678       694748792
    vbr            *value not available*
    mach           0x0      0
    macl           0x0      0
    sr             0x8000   32768

I therefore propose to remove sh_show_regs_command et al. from sh-tdep.c.
If nobody objects, can it just go silently, or should invoking it then
cause an error message, like »Please use the »info all-registers« command
instead of »regs«.«?


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

             reply	other threads:[~2012-05-16 13:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:56 Thomas Schwinge [this message]
2012-05-16 14:26 ` Joel Brobecker
2012-05-16 16:32   ` Thomas Schwinge
2012-05-16 16:58     ` Joel Brobecker
2012-05-16 17:21       ` Thomas Schwinge
2012-05-16 18:47         ` Tom Tromey
2012-05-16 19:06           ` Joel Brobecker
2012-05-16 19:38             ` Maciej W. Rozycki
2012-05-17  0:59               ` Maciej W. Rozycki
2012-05-17 11:10                 ` Mark Kettenis
2012-05-17 11:23                   ` Maciej W. Rozycki
2012-05-17 12:38                     ` Joel Brobecker
2012-05-17 15:23                       ` Mark Kettenis
2012-05-17 15:45                         ` Joel Brobecker
2012-05-17 19:52                           ` Tom Tromey
2012-05-17 20:38                             ` Joel Brobecker
2012-05-18 12:23                               ` Maciej W. Rozycki
2012-05-18 12:39                                 ` Pedro Alves
2012-05-18 12:49                                   ` Joel Brobecker
2012-05-18 13:33                                     ` Pedro Alves
2012-05-18 13:47                                 ` Tom Tromey
2012-05-21 23:36                                   ` Maciej W. Rozycki
2012-05-24 18:05                                     ` Tom Tromey
2012-05-17 19:32         ` Kevin Buettner
2012-05-16 18:36       ` Tom Tromey
2012-05-16 18:36     ` Pedro Alves
2012-05-16 19:36     ` Eli Zaretskii
2012-06-06 18:10     ` Thomas Schwinge
2012-08-10  9:22       ` Thomas Schwinge
2012-08-10 16:20         ` 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=87ehqkrzzw.fsf@schwinge.name \
    --to=thomas@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=macro@codesourcery.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