From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26135 invoked by alias); 3 May 2005 19:53:59 -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 25843 invoked from network); 3 May 2005 19:53:35 -0000 Received: from unknown (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org with SMTP; 3 May 2005 19:53:35 -0000 Received: from zaretski (IGLD-80-230-71-109.inter.net.il [80.230.71.109]) by romy.inter.net.il (MOS 3.5.6-GR) with ESMTP id BDC86474 (AUTH halo1); Tue, 3 May 2005 22:53:23 +0300 (IDT) Date: Tue, 03 May 2005 19:53:00 -0000 From: "Eli Zaretskii" To: gdb@sources.redhat.com Message-ID: <01c55019$Blat.v2.4$95304420@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 Subject: Replace char * with something sensible Reply-to: Eli Zaretskii X-SW-Source: 2005-05/txt/msg00034.txt.bz2 Rumor has it that latest versions of GCC whine about mixing "char *" and "unsigned char *". To fix that, Andrew committed some patches that replace these with a "bfd_byte *", but I think we should not use BFD data types in GDB unless they refer to data structures returned by functions from the BFD library. Possible solutions: . use "void *" (suggested by Mark Kettenis). . define a new data type gdb_byte and use "gdb_byte *". I think Mark's suggestion should be considered first, since it avoids the pain of introducing yet another custom data type.