Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Manoj Verma, Noida" <manojv@noida.hcltech.com>
To: gdb@sources.redhat.com
Subject: remote debugging packets
Date: Fri, 21 Nov 2003 14:00:00 -0000	[thread overview]
Message-ID: <1B3885BC15C7024C845AAC78314766C501033444@EXCH-01> (raw)

Hi,
I am doing remote debugging using GDB server over ethernet. Both host and
target are i386-linux machines.

On the Gdb client side: 
(gdb) break main
(gdb) set debug remote 1
(gdb) step

I see the following (Snapshot-1) packet transaction between Gdb client and
Gdb server. 

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. 

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).

Kindly clarify. 


******************************** Sanpshot-1
*********************************
(gdb) s
Sending packet: $m4000e4f0,1#bd...Ack
Packet received: 55
Sending packet: $M4000e4f0,1:cc#9d...Ack
Packet received: OK
Sending packet: $m40050444,1#5f...Ack
Packet received: 55
Sending packet: $M40050444,1:cc#3f...Ack
Packet received: OK
Sending packet: $s#73...Ack
Packet received: T0505:b8faffbf;04:a0faffbf;08:85840408;
Sending packet: $s#73...Ack
Packet received: T0505:b8faffbf;04:a0faffbf;08:88840408;
Sending packet: $s#73...Ack
Packet received: T0505:b8faffbf;04:a0faffbf;08:8b840408;
Sending packet: $M4000e4f0,1:55#41...Ack
Packet received: OK
Sending packet: $M40050444,1:55#e3...Ack
Packet received: OK
16              z += func1();

****************************************************************************
****

and 

******************************** Sanpshot-2
*********************************
(gdb) c
Continuing.
Sending packet: $Hc0#db...Ack
Packet received: OK
Sending packet: $s#73...Ack
Packet received: T0505:b8faffbf;04:98faffbf;08:f5840408;
Sending packet: $m8048466,1#3e...Ack
Packet received: c7
Sending packet: $M8048466,1:cc#1e...Ack
Packet received: OK
Sending packet: $m80484ce,1#9a...Ack
Packet received: c7
Sending packet: $M80484ce,1:cc#7a...Ack
Packet received: OK
Sending packet: $m4000e4f0,1#bd...Ack
Packet received: 55
Sending packet: $M4000e4f0,1:cc#9d...Ack
Packet received: OK
Sending packet: $Hc0#db...Ack
Packet received: OK
Sending packet: $c#63...Ack
Packet received: T0505:98faffbf;04:8cfaffbf;08:fb840408;

****************************************************************************
****

Any clarification would be appreciated.


             reply	other threads:[~2003-11-21 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21 14:00 Manoj Verma, Noida [this message]
2003-11-21 14:25 ` Mark Salter
2003-11-21 14:32 Manoj Verma, Noida
2003-11-21 14:52 ` Mark Salter
2003-11-21 15:15 Manoj Verma, Noida
2003-11-21 16:06 ` Mark Salter
2003-11-22  8:44 Manoj Verma, Noida
2003-11-22  9:26 ` Ramana Radhakrishnan
2003-11-22 13:46 ` 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=1B3885BC15C7024C845AAC78314766C501033444@EXCH-01 \
    --to=manojv@noida.hcltech.com \
    --cc=gdb@sources.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