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: Mark Salter <msalter at redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 21 Nov 2003 20:48:19 +0530
- Subject: RE: remote debugging packets
Let me explain my concern in this way...
I have following C snippet:
...
for(i=0; i<100; i++) // say line #xx
*b0++ = *b1++; // say line #yy
...
and the assembly instruction corresponding to it is:
...
lc = 100;
rep(lc) *b0++ = *b1++;
...
I set the breakpoint to both of these lines xx & yy.
Now when I am at XX, I say 'Continue'. If it steps first then it comes to
line #yy. Then if it continues, then I will not see my program stopping at
YY where it should.
Or is it like, before proceeding from line #YY the debugger looks for some
traps present at that particular line and then continues..
Pl. correct me if I am wrong.
Thanks..
> -----Original Message-----
> From: Mark Salter [mailto:msalter@redhat.com]
> Sent: Friday, November 21, 2003 8:22 PM
> To: manojv@noida.hcltech.com
> Cc: gdb@sources.redhat.com
> Subject: Re: remote debugging packets
>
>
> >>>>> Manoj Verma, Noida writes:
>
> >> > 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?
>
> It is certainly correct behavior. I don't see any problem with
> your scenario.
>
> --Mark
>
>