From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29570 invoked by alias); 2 Dec 2002 18:55:20 -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 29562 invoked from network); 2 Dec 2002 18:55:19 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 2 Dec 2002 18:55:19 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18IxbR-0003Wg-00; Mon, 02 Dec 2002 14:55:41 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18IvjL-0004az-00; Mon, 02 Dec 2002 13:55:43 -0500 Date: Mon, 02 Dec 2002 10:55:00 -0000 From: Daniel Jacobowitz To: David Mc Kenna Cc: gdb@sources.redhat.com Subject: Re: GDB speed using Remote Serial Protocol Message-ID: <20021202185543.GA17558@nevyn.them.org> Mail-Followup-To: David Mc Kenna , gdb@sources.redhat.com References: <3debabab.66df.0@esatclear.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3debabab.66df.0@esatclear.ie> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00020.txt.bz2 No, you missed my gist. With debug info printing, GDB takes a little bit longer (because it has to do the printing). Something is being sent too quickly, and being dropped and then eventually retried. On Mon, Dec 02, 2002 at 06:51:23PM +0000, David Mc Kenna wrote: > I would agree with this except that with debug info switched on it is much faster > than with it switched off. What is the difference in code execution within GDB > with debug info switched off? > > Cheers, > Dave > > >On Mon, Dec 02, 2002 at 05:27:04PM +0000, David Mc Kenna wrote: > >> Hi all, > >> > >> At present I have an outline for a stub ( GDB RSP -> uController -> Jtag > ) for > >> an Arm7TDMi. I have successfully implemented the GDB -> uController side > of > >> the equation. Here I have two questions. > >> > >> Is there another way of seeing what GDB sends to the serial port without > enabling > >> debug info within GDB ?, i.e. without using the commands : > >> "set debug remote 1" & " set debug serial 1" > >> > >> My second questions relates to the first. With debug info switched on ( "set > > >> debug remote 1" & " set debug serial 1"), a single step talks < 1 second > to > >> complete, including all the debug info being written to the screen. Yet when > > >> I switch off this info the single step time starts at < 1 second but soon > mushrooms > >> to ~ 5 seconds. > >> > >> I have tried this on gdb v5 and gdb v5.2.1 with the same results. > >> GDB configured as arm-elf > >> > >> > >> Any ideas?? > > > >Sounds like something is being sent more quickly than your > >stub/controller/whatever is ready to handle it. > > > >What I recommend in this case is writing (or getting; rproxy may be > >able to do this?) a stub which just connects a TCP port and a serial > >port; forwards data from one to the other, and logs. > > > >-- > >Daniel Jacobowitz > >MontaVista Software Debian GNU/Linux Developer > > > > > -- > http://www.iol.ie > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer