From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30974 invoked by alias); 16 May 2003 20:04:00 -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 30930 invoked from network); 16 May 2003 20:04:00 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 16 May 2003 20:04:00 -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 QAA23528; Fri, 16 May 2003 16:00:20 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id QAA06511; Fri, 16 May 2003 16:03:58 -0400 Message-ID: <078501c31be6$52622e60$0202040a@catdog> From: "Kris Warkentin" To: "Daniel Jacobowitz" Cc: "Quality Quorum" , "Gdb@Sources.Redhat.Com" References: <075801c31be0$c5d0de10$0202040a@catdog> <20030516192900.GA2984@nevyn.them.org> Subject: Re: (remote) hellishly slow single stepping over library calls Date: Fri, 16 May 2003 20:04: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/msg00252.txt.bz2 > > 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? cheers, Kris