From: jtc@redback.com (J.T. Conklin)
To: Kevin Hilman <khilman@equator.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: 'info registers' only when hit a breakpoint
Date: Fri, 09 Jun 2000 16:24:00 -0000 [thread overview]
Message-ID: <5mhfb2tp4g.fsf@jtc.redback.com> (raw)
In-Reply-To: <r2vgztcgsh.fsf@bobdog.equator.com>
>>>>> "Kevin" == Kevin Hilman <khilman@equator.com> writes:
Kevin> I'm working on a target implementation for a new chip our company is
Kevin> developing. The current hardware implementation only saves register
Kevin> state (for 'info registers') in the frame in which a breakpoint was
Kevin> hit. The other frames only have minimal information (for function
Kevin> args, local variables etc.)
Kevin>
Kevin> Therefore, I want 'info registers' to not work if someone tries
Kevin> an 'up' for example.
'info registers' displays the current values of the registers. The
output does not change when you change the frame with frame/up/down.
I guess I'm not sure I understand what you want/need.
--jtc
--
J.T. Conklin
RedBack Networks
prev parent reply other threads:[~2000-06-09 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 13:01 Kevin Hilman
2000-06-09 16:24 ` J.T. Conklin [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=5mhfb2tp4g.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=gdb@sourceware.cygnus.com \
--cc=khilman@equator.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).