From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin Hilman <khilman@equator.com>
To: gdb@sourceware.cygnus.com
Subject: 'info registers' only when hit a breakpoint
Date: Thu, 01 Jun 2000 13:01:00 -0000
Message-id: <r2vgztcgsh.fsf@bobdog.equator.com>
X-SW-Source: 2000-06/msg00006.html

I'm working on a target implementation for a new chip our company is
developing.  The current hardware implementation only saves register
state (for 'info registers') in the frame in which a breakpoint was
hit.  The other frames only have minimal information (for function
args, local variables etc.)

Therefore, I want 'info registers' to not work if someone tries an
'up' for example.

Looking at registers_info(), it looks like I want to set
'target_has_registers' to zero.  I'm wondering where is the best place
to implement this feature.  It doesn't seem like modifying
up_command() is the right place since I'd have to keep track of how
many times someone has done up/down.

Any ideas?

NOTE: I'm currently working with gdb 4.17.

-- 
Kevin Hilman               ---  Equator Technologies Inc.
khilman@equator.com        ---  Seattle, WA USA