From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3932 invoked by alias); 11 Nov 2010 11:58:48 -0000 Received: (qmail 3922 invoked by uid 22791); 11 Nov 2010 11:58:47 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-fx0-f41.google.com (HELO mail-fx0-f41.google.com) (209.85.161.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Nov 2010 11:58:43 +0000 Received: by fxm20 with SMTP id 20so1243554fxm.0 for ; Thu, 11 Nov 2010 03:58:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.79.12 with SMTP id n12mr130952fak.53.1289476688765; Thu, 11 Nov 2010 03:58:08 -0800 (PST) Received: by 10.223.86.139 with HTTP; Thu, 11 Nov 2010 03:58:08 -0800 (PST) In-Reply-To: <201011111100.02615.pedro@codesourcery.com> References: <201011111100.02615.pedro@codesourcery.com> Date: Thu, 11 Nov 2010 11:58:00 -0000 Message-ID: Subject: Re: gdbserver delayed packet event issue From: "karthikeyan.s" To: Pedro Alves Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00049.txt.bz2 Will try 7.2 but in the meantime, The complete version is 7.1.50.20100416. On Thu, Nov 11, 2010 at 4:30 PM, Pedro Alves wrote: > 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. =A0All snapshots from the 7.1 release up to > the 7.2 release were named like that. =A0There should be a date > after the "50". =A0Which is it? =A0There 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 > --=20 --- S. Karthikeyan | +919980814745 ---