From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12310 invoked by alias); 16 May 2003 23:10:31 -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 12157 invoked from network); 16 May 2003 23:10:27 -0000 Received: from unknown (HELO TheWorld.com) (199.172.62.103) by sources.redhat.com with SMTP; 16 May 2003 23:10:27 -0000 Received: from shell.TheWorld.com (shell01.TheWorld.com [199.172.62.241]) by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id h4GNAL4h003278; Fri, 16 May 2003 19:10:22 -0400 Received: from localhost (qqi@localhost) by shell.TheWorld.com (8.9.3/8.9.3) with ESMTP id TAA4510858; Fri, 16 May 2003 19:10:21 -0400 (EDT) X-Authentication-Warning: shell01.TheWorld.com: qqi owned process doing -bs Date: Fri, 16 May 2003 23:10:00 -0000 From: Quality Quorum To: Kris Warkentin cc: Daniel Jacobowitz , "Gdb@Sources.Redhat.Com" Subject: Re: (remote) hellishly slow single stepping over library calls In-Reply-To: <078501c31be6$52622e60$0202040a@catdog> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-05/txt/msg00253.txt.bz2 On Fri, 16 May 2003, Kris Warkentin wrote: > > > I'll look into implementing that sort of thing on our end. > > > > It should be pretty straightforward to do. When you get the right > > registers, it's quite effective, too. > > I took a look at our notify message and it already has space for various > registers in it depending on what the notification is for (ie. single step, > break, etc.) I should be able to stuff them on the target end and supply > them every time gdb stops. Other than empirically, where can I discover > what registers are needed for various targets? I'm thinking IP for everyone > but are some going to want stack and frame pointers as well? I suppose that a program counter, a frame pointer and a stack pointer will be enough. It is easy to test, if gdb needs more resiters it will pull them all in. > > cheers, > > Kris > Thanks, Aleksey