This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: remote debugging packets
- From: Mark Salter <msalter at redhat dot com>
- To: manojv at noida dot hcltech dot com
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 21 Nov 2003 09:25:56 -0500 (EST)
- Subject: Re: remote debugging packets
- References: <1B3885BC15C7024C845AAC78314766C501033444@EXCH-01>
>>>>> Manoj Verma, Noida writes:
> My question is,
> 1) I did the "step" only once but why there are three packets (sometimes two
> packets) corresponding to the "step" ($s#73...Ack) as shown below in
> sanpshot-1, evenif the correct response is received for the first packet.
"step" is used to step past a line of source code. The $s packet tells
the target to step past a machine instruction. Apparently in this case,
the source code line corresponds to three machine instructions.
> 2) On the Gdb client side when I continue, "(gdb) continue", why it first
> sends a packet ($s#73...Ack) and then the packet ($c#63...Ack) as shown
> below in sanpshot-2 ? It should only send the packet ($c#63...Ack).
This is expected. GDB has to single-step past the one machine instruction
before re-inserting any breakpoints and continuing.
--Mark