From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 916 invoked by alias); 19 May 2005 03:33:44 -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 824 invoked from network); 19 May 2005 03:33:40 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 19 May 2005 03:33:40 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DYbn1-0008FR-BS; Wed, 18 May 2005 23:33:39 -0400 Date: Thu, 19 May 2005 05:37:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: Richard Henderson , gdb-patches@sources.redhat.com Subject: Re: Question: Checking register value in buffer Message-ID: <20050519033339.GA31674@nevyn.them.org> Mail-Followup-To: Joel Brobecker , Richard Henderson , gdb-patches@sources.redhat.com References: <20050519020443.GP1462@adacore.com> <20050519022256.GA8204@redhat.com> <20050519024857.GY12565@adacore.com> <20050519030349.GA8255@redhat.com> <20050519032332.GZ12565@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050519032332.GZ12565@adacore.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00467.txt.bz2 On Thu, May 19, 2005 at 01:23:32PM +1000, Joel Brobecker wrote: > Isn't this assument that LONGEST is exactly 64 bits? I think > extract_signed_integer expands the value held in the given buffer > to fit the size of LONGEST. Here is the implementation: If you're confusing yourself with sign extension, use ULONGEST instead. But this isn't the only thing that would break in GDB with 128-bit types. You really don't need to be this paranoid. -- Daniel Jacobowitz CodeSourcery, LLC