From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7757 invoked by alias); 21 Nov 2003 14:52:07 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7750 invoked from network); 21 Nov 2003 14:52:07 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 21 Nov 2003 14:52:07 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id hALEq7H10518 for ; Fri, 21 Nov 2003 09:52:07 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id hALEq6w27942; Fri, 21 Nov 2003 09:52:06 -0500 Received: from deneb.localdomain (msalter.cipe.redhat.com [10.0.0.36]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id hALEq6HT018890; Fri, 21 Nov 2003 09:52:06 -0500 Received: by deneb.localdomain (Postfix, from userid 500) id 155B87879F; Fri, 21 Nov 2003 09:52:06 -0500 (EST) From: Mark Salter To: manojv@noida.hcltech.com Cc: gdb@sources.redhat.com In-reply-to: <1B3885BC15C7024C845AAC78314766C50103348D@EXCH-01> (manojv@noida.hcltech.com) Subject: Re: remote debugging packets References: <1B3885BC15C7024C845AAC78314766C50103348D@EXCH-01> Message-Id: <20031121145206.155B87879F@deneb.localdomain> Date: Fri, 21 Nov 2003 14:52:00 -0000 X-SW-Source: 2003-11/txt/msg00194.txt.bz2 >>>>> 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