From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29094 invoked by alias); 27 Jan 2003 20:54:57 -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 29087 invoked from network); 27 Jan 2003 20:54:56 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 27 Jan 2003 20:54:56 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id PAA31905; Mon, 27 Jan 2003 15:45:17 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id PAA23252; Mon, 27 Jan 2003 15:54:55 -0500 Message-ID: <10cd01c2c646$4c9cccb0$0202040a@catdog> From: "Kris Warkentin" To: "Andrew Cagney" Cc: References: <105c01c2c63e$0b5de4d0$0202040a@catdog> <3E35991E.9060106@redhat.com> Subject: Re: integer types in gdb code Date: Mon, 27 Jan 2003 20:54:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-01/txt/msg00447.txt.bz2 > > I'm having trouble cleaning up our code to compile on various targets. > > > > It seems like most targets have uint32_t, int8_t, etc. defined but not > > always (ie. cygwin). Is there a 'gdb approved' header or set of defines > > that works consistently everywhere? I'd like to be able to use something > > consistently in all of our code without having to type in 'unsigned long > > long' and such. > > CORE_ADDR ~= void * > LONGEST ~= long > ULONGEST ~= unsigned long No 16 and 8 bit constructs? Also, what if you want to guarantee the number of bits? From defs.h it looks to me like LONGEST could be 32 or 64 bits, so if you're reading structures over the wire, you could have problems. Kris