From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29007 invoked by alias); 11 Nov 2010 11:00:13 -0000 Received: (qmail 28994 invoked by uid 22791); 11 Nov 2010 11:00:11 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Nov 2010 11:00:07 +0000 Received: (qmail 13651 invoked from network); 11 Nov 2010 11:00:05 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 11 Nov 2010 11:00:05 -0000 From: Pedro Alves To: gdb@sourceware.org Subject: Re: gdbserver delayed packet event issue Date: Thu, 11 Nov 2010 11:00:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.33-29-realtime; KDE/4.4.5; x86_64; ; ) Cc: "karthikeyan.s" References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011111100.02615.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00048.txt.bz2 On Thursday 11 November 2010 05:52:17, karthikeyan.s wrote: > Hi, > I am seeing an issue with the gdb remote debugging, this is gdb 7.1.50 > version. I have marked the erroneous states with line --> below. > > gdbserver sometimes gets a delayed event for the packet > QStartNoAckMode sent from the host. In the case pasted below gdbserver > gets two events clubbed together when the client has sent the second > "QStartNoAckMode" packet after its timeout. At this stage, gdbserver > ends up sending two "$OK" while the client is expecting only one and > the state gets messed up between client and server. > > 1) It seems that the client does not handle issues with the network. > Instead it assumes the packet is lost on a timeout. > 2) Why doesn't gdbserver get an event on the first request itself. I > used writeshark on the client side to confirm the packet is being > sent. And tcpdump on the remote side to see that the packet does come > in at the target. "7.1.50" is quite vague. All snapshots from the 7.1 release up to the 7.2 release were named like that. There should be a date after the "50". Which is it? There was a similar problem fixed around April/March 2010. You could also try switching to 7.2 or a later snapshot and confirm the problem is gone. -- Pedro Alves