From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31012 invoked by alias); 16 May 2003 18:25:12 -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 30979 invoked from network); 16 May 2003 18:25:10 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 16 May 2003 18:25:10 -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 OAA19603 for ; Fri, 16 May 2003 14:21:31 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA31046 for ; Fri, 16 May 2003 14:25:08 -0400 Message-ID: <071001c31bd8$841db090$0202040a@catdog> From: "Kris Warkentin" To: "Gdb@Sources.Redhat.Com" Subject: (remote) hellishly slow single stepping over library calls Date: Fri, 16 May 2003 18:25: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/msg00245.txt.bz2 When debugging using our QNX pdebug remote protocol and single stepping over a library call like printf, it takes a LOOOONG time. I'm talking like two or three minutes. A 'next' is fine but looking at the output of running our pdebug server in verbose mode, gdb is doing step, step, step, all the way through the whole library call. Every single step results in fetching registers and there is a huge amount of wire traffic generated. This didn't happen with older (ie 5.0) gdbs which didn't seem to know how to single step through our shared lib code but now that it does, this is pretty painful. Obviously it makes more sense to 'next' over a library call, especially if you don't want to go into it but the question is, can anyone think of a way to optimize this? I though of putting in a hack like: if (reg == PC_REGNUM) only_get_pc(); to avoid fetching the whole regset but it probably won't make that much difference since there's still a packet over the wire each time and most regsets fit in one packet anyway. Would this problem also exist with the normal remote protocol? (stupid users...clicking step instead of next....;-) cheers, Kris