From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26119 invoked by alias); 8 Oct 2005 16:00:14 -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 26023 invoked by uid 22791); 8 Oct 2005 16:00:11 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 08 Oct 2005 16:00:11 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1EOH7F-0004DT-C2; Sat, 08 Oct 2005 12:00:05 -0400 Date: Sat, 08 Oct 2005 16:00:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: "Nathan J. Williams" , gdb-patches@sourceware.org Subject: Re: RFA: general prologue analysis framework Message-ID: <20051008160004.GA16168@nevyn.them.org> Mail-Followup-To: Jim Blandy , "Nathan J. Williams" , gdb-patches@sourceware.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00070.txt.bz2 On Sat, Oct 08, 2005 at 12:01:17AM -0700, Jim Blandy wrote: > I'm not sure this has any practical value, but it's fun to think > about. I wonder if there are cool things we could do if we had such > detailed information about the machine code we were looking at. Could > we step through heavily reordered code better? I can't see how it would be useful for that; but I've written before about the sorts of things we could do with detailed knowledge of what machine code does. For instance, you can single-step over breakpoints much more efficiently in some caess. -- Daniel Jacobowitz CodeSourcery, LLC