This is the mail archive of the
mailing list for the GDB project.
'info registers' only when hit a breakpoint
- To: gdb at sourceware dot cygnus dot com
- Subject: 'info registers' only when hit a breakpoint
- From: Kevin Hilman <khilman at equator dot com>
- Date: 01 Jun 2000 13:01:02 -0700
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.
NOTE: I'm currently working with gdb 4.17.
Kevin Hilman --- Equator Technologies Inc.
email@example.com --- Seattle, WA USA