From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27866 invoked by alias); 8 Jun 2005 17:01:03 -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 27810 invoked from network); 8 Jun 2005 17:00:57 -0000 Received: from unknown (192.220.74.81) by sourceware.org with QMTP; 8 Jun 2005 17:00:57 -0000 Received: (qmail 84943 invoked by uid 19025); 8 Jun 2005 17:00:57 -0000 Date: Wed, 08 Jun 2005 17:01:00 -0000 From: Jason Molenda To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com, kettenis@jive.nl Subject: Re: The gdb x86 function prologue parser Message-ID: <20050608100057.A84229@molenda.com> References: <85C775AE-3B05-431E-96D2-49EA9D1413E6@apple.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from eliz@gnu.org on Wed, Jun 08, 2005 at 05:52:13PM +0300 X-SW-Source: 2005-06/txt/msg00065.txt.bz2 Hi Eli, On Wed, Jun 08, 2005 at 05:52:13PM +0300, Eli Zaretskii wrote: > > +#include > > I don't think we can use stdint.h freely, as we still don't require a > C9x compiler. I see you needed it for things like uint8_t and > uint32_t, which should be easily replaceable by suitable standard x86 > types. I'll change the code. I've become spoiled and taken to assuming these types are available. > Last, but not least, I'd surely appreciate some write-up, even in > plain ASCII, about how prologue analyzers in general and the x86 one > in particular work: that stuff is sorely needed in gdbint.texinfo. OK, I'll look over gdbint next week and see what it says and where something like that might fit in. Thanks for the comments, J