From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26328 invoked by alias); 7 Mar 2005 21:32:48 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26256 invoked from network); 7 Mar 2005 21:32:45 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 7 Mar 2005 21:32:45 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1D8PqD-0007Pm-8f; Mon, 07 Mar 2005 16:32:41 -0500 Date: Mon, 07 Mar 2005 21:32:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis , gdb-patches@sources.redhat.com Subject: Re: [RFA] New GDB target iq2000 Message-ID: <20050307213241.GA28365@nevyn.them.org> Mail-Followup-To: Mark Kettenis , gdb-patches@sources.redhat.com References: <20050222114141.GA18314@cygbert.vinschen.de> <20050303173443.GD18681@nevyn.them.org> <20050304094605.GU2839@cygbert.vinschen.de> <20050304141439.GA30249@nevyn.them.org> <20050304150129.GF2839@cygbert.vinschen.de> <20050304220104.GA14522@nevyn.them.org> <200503051128.j25BSruw007318@elgar.sibelius.xs4all.nl> <20050305164451.GA8398@nevyn.them.org> <200503051813.j25IDCxt016723@elgar.sibelius.xs4all.nl> <20050305193739.GA13304@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050305193739.GA13304@nevyn.them.org> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00099.txt.bz2 On Sat, Mar 05, 2005 at 02:37:39PM -0500, Daniel Jacobowitz wrote: > I'm not talking about an ultra-specialized "simulator" the way that > current GDB prologue analyzers work; I'm talking about most of a > complete architecture simulator, with appropriate hooks to tell GDB > what it wants to know. There's plenty of other ways we could use this > information. > > Here's one I've been thinking about in particular: some instructions > are "safe" to simulate on a running process, though not all. When a > breakpoint covers an instruction which is "safe", we can simulate the > instruction instead of having to remove the breakpoint and single-step. > Huge win with threads. It occured to me (late, but better than never) that generating this sort of thing from a CGEN description would not be too hard... for someone who spoke Scheme, anyway. Not that I'm volunteering to write the missing cgen descriptions. But it would be an interesting experiment for one of the five ports that already have one (cris, frv, iq2000, m32r, sh). -- Daniel Jacobowitz CodeSourcery, LLC