From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6795 invoked by alias); 29 Jan 2008 19:28:14 -0000 Received: (qmail 6776 invoked by uid 22791); 29 Jan 2008 19:28:13 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Jan 2008 19:27:43 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 1CF2C98151; Tue, 29 Jan 2008 19:27:42 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 068C29811F; Tue, 29 Jan 2008 19:27:41 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JJw7R-0003F9-06; Tue, 29 Jan 2008 14:27:41 -0500 Date: Tue, 29 Jan 2008 19:33:00 -0000 From: Daniel Jacobowitz To: =?iso-8859-1?Q?Zolt=E1n_Fily=F3?= Cc: gdb-patches@sourceware.org Subject: Re: remote protocol patch Message-ID: <20080129192740.GC9019@caradoc.them.org> Mail-Followup-To: =?iso-8859-1?Q?Zolt=E1n_Fily=F3?= , gdb-patches@sourceware.org References: <2D8B78375B46EF4C85EE21B9EB64350A062ED604@esealmw103.eemea.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2D8B78375B46EF4C85EE21B9EB64350A062ED604@esealmw103.eemea.ericsson.se> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00714.txt.bz2 On Wed, Jan 16, 2008 at 11:11:26AM +0100, Zoltán Filyó wrote: > > Hi, > > I found that the serial remote protocol runs into a deadlock when > the serial line is noisy. Below a gdb log fragment with original > code: My strong recommendation is to not use the GDB serial protocol over a noisy line. There's other problems, for instance with packets which have different effects when repeated. > r +$S05#b8 > w +$g#67 > r > w $g#67 > r > w $g#67 > r > w $g#67 > r > w - > r > w - > r > w -+ > > infinitely. Because the target side NetBSD kernel throws all > characters until get a new packet start ('$') char. What's happened here, the four repetitions of $g#67 were all completely lost, and then GDB timed out? IMO, we should treat some of these timeouts as fatal to the protocol conversation. -- Daniel Jacobowitz CodeSourcery