From: "Manoj Verma, Noida" <manojv@noida.hcltech.com>
To: gdb@sources.redhat.com
Cc: Mark Salter <msalter@redhat.com>
Subject: RE: remote debugging packets
Date: Fri, 21 Nov 2003 14:32:00 -0000 [thread overview]
Message-ID: <1B3885BC15C7024C845AAC78314766C50103348D@EXCH-01> (raw)
> -----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
>
next reply other threads:[~2003-11-21 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 14:32 Manoj Verma, Noida [this message]
2003-11-21 14:52 ` Mark Salter
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 8:44 Manoj Verma, Noida
2003-11-22 9:26 ` Ramana Radhakrishnan
2003-11-22 13:46 ` Mark Salter
2003-11-21 15:15 Manoj Verma, Noida
2003-11-21 16:06 ` Mark Salter
2003-11-21 14:00 Manoj Verma, Noida
2003-11-21 14:25 ` Mark Salter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1B3885BC15C7024C845AAC78314766C50103348D@EXCH-01 \
--to=manojv@noida.hcltech.com \
--cc=gdb@sources.redhat.com \
--cc=msalter@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox