From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26460 invoked by alias); 2 Apr 2003 10:13:32 -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 26453 invoked from network); 2 Apr 2003 10:13:31 -0000 Received: from unknown (HELO TYO202.gate.nec.co.jp) (202.32.8.202) by sources.redhat.com with SMTP; 2 Apr 2003 10:13:31 -0000 Received: from mailgate3.nec.co.jp ([10.7.69.192]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id h32ADTU02873; Wed, 2 Apr 2003 19:13:29 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) id h32ADTt25495; Wed, 2 Apr 2003 19:13:29 +0900 (JST) Received: from edtmg04.lsi.nec.co.jp ([10.26.17.201]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id h32ADR505091; Wed, 2 Apr 2003 19:13:28 +0900 (JST) Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg04.lsi.nec.co.jp (8.9.3+3.2W/3.7W_EDC_Ver.1.0) with ESMTP id TAA04586; Wed, 2 Apr 2003 19:13:27 +0900 (JST) Received: from mcspd15.ucom.lsi.nec.co.jp (mcspd15 [10.30.114.174]) by mcsss2.ucom.lsi.nec.co.jp (8.12.8/8.12.8/EDcg v2.01-mc/1046780839) with ESMTP id h32ADQNH004018; Wed, 2 Apr 2003 19:13:26 +0900 (JST) Received: by mcspd15.ucom.lsi.nec.co.jp (Postfix, from userid 31295) id DA6D73724; Wed, 2 Apr 2003 19:13:25 +0900 (JST) To: gdb@sources.redhat.com Subject: testing current target (in gdb code) Reply-To: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop From: Miles Bader Date: Wed, 02 Apr 2003 10:13:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-04/txt/msg00019.txt.bz2 Hi, I'm currently working on making gdb's v850 support work on real CPUs, and unfortunately I can't get the hardware single-stepping to work consistently (the hardware has lots of weird restrictions, and by doing lots of tricks I can get it to work on some processors, but not others). So I'd like to use GDB's software-single-stepping facility for those cases where I can't use hardware (thanks to Kevin Buettner who told me where to find it!); however, I'd still like to use hardware single-stepping when possible as it seems likely to always be reliable in some corner case or another, no matter how careful I am. In particular, `hardware' single-stepping works great in GDB's simulator. I guess I can do this sort of thing by defining SOFTWARE_SINGLE_STEP_P to call a function that looks at the current target and returns an appropriate boolean for it (defaulting to 1 I suppose). However I'm not sure how to test the current target; any pointers? Or am I on the wrong track entirely, and there's a better way to do what I want? Thanks for any tips, -Miles -- `Life is a boundless sea of bitterness'