'info registers' only when hit a breakpoint

'info registers' only when hit a breakpoint

[Kevin Hilman]

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

Re: 'info registers' only when hit a breakpoint

[J.T. Conklin]

>>>>> "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