This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: remote debugging packets
- From: "Manoj Verma, Noida" <manojv at noida dot hcltech dot com>
- To: gdb at sources dot redhat dot com
- Cc: Mark Salter <msalter at redhat dot com>
- Date: Fri, 21 Nov 2003 20:04:46 +0530
- Subject: RE: remote debugging packets
> -----Original Message-----
> From: Mark Salter [mailto:msalter@redhat.com]
> Sent: Friday, November 21, 2003 7:56 PM
> To: manojv@noida.hcltech.com
> Cc: gdb@sources.redhat.com
> Subject: Re: remote debugging packets
>
>
> >>>>> 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.
>
This is fine.
> > 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.
>
But consider the scenario when I have breakpoints set on two consecutive
lines. Will in this case also this behavior is justified?
> --Mark
>