public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Stan Cox <scox@redhat.com>
Cc: Nurdin Premji <npremji@redhat.com>, Frysk List <frysk@sourceware.org>
Subject: Re: Regs command
Date: Tue, 31 Jul 2007 23:50:00 -0000	[thread overview]
Message-ID: <46AFCAC3.1080309@redhat.com> (raw)
In-Reply-To: <1185846259.9874.18.camel@multics.rdu.redhat.com>

Stan Cox wrote:
> Nice.  Could we also have hex output as with gdb's "info registers"?
> Is there an fhpd request "regs"?  If not would "registers" be a more
> descriptive name?
>   
Yes, I would find hex more useful, too. I guess we could go a few ways 
here. Have a fhpd wide format command (to switch between decimal, hex, 
binary, octal); have the regs print out hex with the decimal equivalent 
in brackets, or just print out hex.

The biggie for me is hex output.

Regards

Phil

      reply	other threads:[~2007-07-31 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 19:53 Nurdin Premji
2007-07-31  1:45 ` Stan Cox
2007-07-31 23:50   ` Phil Muldoon [this message]

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=46AFCAC3.1080309@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=npremji@redhat.com \
    --cc=scox@redhat.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).