From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29372 invoked by alias); 8 Mar 2012 23:00:30 -0000 Received: (qmail 29310 invoked by uid 22791); 8 Mar 2012 23:00:28 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 08 Mar 2012 23:00:16 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 7C9821C694B for ; Thu, 8 Mar 2012 18:00:15 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id TzeCEeD8ZkXi for ; Thu, 8 Mar 2012 18:00:15 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 4599C1C679E for ; Thu, 8 Mar 2012 18:00:15 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 3E9FB145615; Thu, 8 Mar 2012 15:00:08 -0800 (PST) Date: Thu, 08 Mar 2012 23:00:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: Re: [RFA] ax-gdb: Do not treat enums and bools as integers. Message-ID: <20120308230008.GV2853@adacore.com> References: <1331240440-13559-1-git-send-email-brobecker@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1331240440-13559-1-git-send-email-brobecker@adacore.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00302.txt.bz2 > gdb/ChangeLog: > > * ax-gdb.c (gen_usual_unary): Remove special handling of > enum and bool types. > > Tested on x86_64-linux. I'll try to come up with an example that > reproduces the problem without using the proprietary testcase. Unfortunately, my attempts have failed. It comes from the fact that somehow, the bytes right next to my parameter value are null instead of being some random non-null value, thus hiding the problem. -- Joel