This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: GDB-Protocol: Cycle step command?
- To: Andrew Cagney <ac131313@cygnus.com>
- Subject: Re: GDB-Protocol: Cycle step command?
- From: jtc@redback.com (J.T. Conklin)
- Date: 17 Jun 1999 11:17:48 -0700
- Cc: gdb@sourceware.cygnus.com
- References: <376838C8.D287322C@cygnus.com>
- Reply-To: jtc@redback.com
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> Hello, I'd like to propose that the GDB remote protocol be
Andrew> extended to support a cycle step command. This command would
Andrew> be used when either interacting with physical control devices
Andrew> such as JTAG or (more often) cycle accurate simulators.
Andrew>
Andrew> Possible syntaxes include:
Andrew> QCycle=<NR>
Andrew> and i<NR>
Andrew>
Andrew> comments suggestions additional data people thing may be
Andrew> needed. Unlike the ``S'' and ``C'' commands I've not included
Andrew> an address. Changing the address in a cycle accurate model
Andrew> can get very complex.
This seems incomplete.
If you have a command to step through processor cycles, don't you also
need cooresponding commands to extract processor state (pipeline, tlb,
cache, btb, etc.). Without such commands, I fail to see the value in
being able to step in this manner.
--jtc
--
J.T. Conklin
RedBack Networks