From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4766 invoked by alias); 16 May 2003 18:57:59 -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 4756 invoked from network); 16 May 2003 18:57:59 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 16 May 2003 18:57:59 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3p2/8.9.3) with ESMTP id OAA20803; Fri, 16 May 2003 14:54:20 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA01247; Fri, 16 May 2003 14:57:57 -0400 Message-ID: <072601c31bdd$19bb8d30$0202040a@catdog> From: "Kris Warkentin" To: "Theodore A. Roth" Cc: "Gdb@Sources.Redhat.Com" References: <071001c31bd8$841db090$0202040a@catdog> Subject: Re: (remote) hellishly slow single stepping over library calls Date: Fri, 16 May 2003 18:57:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-05/txt/msg00247.txt.bz2 > Not sure if this is totally related (how does pdebug differ from rsp?) > but maybe a solution could help avr users too. > > Some sort of optimization here would be boon for avr users. In our > case we use gdb to talk to our avarice program > (http://sourceforge.net/projects/avarice) which talks to a jtagice box > which in turn talks to the actual target device via a jtag interface. > Single stepping is painfully slow: step, wait 1-5 seconds, step, etc. > > The bottleneck for us not so much sending info over the wire via rsp, > but in reading the registers from the device via jtag. If we could > reduce the number registers that need to be read at each step, I think > it could speed things up. Well, once upon a time, we would get one register at a time. Then we decided to optimize and get the whole regset since we can supply them to gdb and then it won't ask for any more. The only place this really optimizes is when you're asking for more than one per stop which isn't the case when single stepping. Like I said before though, in our case it might not matter since we have to send a packet anyway and it costs no more to have the whole regset in there. You, however, I could see really benefitting from this if the jtag is relatively slow at fetching registers and you have to do it one at a time. There isn't any way to tell the jtag to send a whole set I suppose? cheers, Kris