From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26305 invoked by alias); 6 Aug 2008 20:37:34 -0000 Received: (qmail 26296 invoked by uid 22791); 6 Aug 2008 20:37:34 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Aug 2008 20:36:59 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m76KasFt027760; Wed, 6 Aug 2008 16:36:54 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m76KarKt003012; Wed, 6 Aug 2008 16:36:53 -0400 Received: from opsy.redhat.com (vpn-10-34.bos.redhat.com [10.16.10.34]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m76Kaq7g007564; Wed, 6 Aug 2008 16:36:53 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 5056A378159; Wed, 6 Aug 2008 14:36:53 -0600 (MDT) To: Thiago Jung Bauermann Cc: Neo Jia , gdb ml Subject: Re: gdb plugin status? References: <5d649bdb0808031010g6330a442xec0415a387d23163@mail.gmail.com> <20080803173108.GA20590@caradoc.them.org> <5d649bdb0808031042i7210287djb225792fc7221319@mail.gmail.com> <1217800323.29321.3.camel@localhost.localdomain> <1217800536.29321.7.camel@localhost.localdomain> <5d649bdb0808040042o34b759edxe6c11e16588214f6@mail.gmail.com> <1217860034.7578.8.camel@localhost.localdomain> <5d649bdb0808050033k212fb93arc4e8b7ff8f9b1a7f@mail.gmail.com> <1217943660.4534.1.camel@localhost.localdomain> <5d649bdb0808051553g6ee22cbfr80cfa43cd56e870c@mail.gmail.com> <1217993159.4534.47.camel@localhost.localdomain> <1218001435.4534.60.camel@localhost.localdomain> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Wed, 06 Aug 2008 20:37:00 -0000 In-Reply-To: <1218001435.4534.60.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Wed\, 06 Aug 2008 02\:43\:55 -0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00114.txt.bz2 >>>>> "Thiago" == Thiago Jung Bauermann writes: Tom> FWIW, my build uses -fno-strict-aliasing, which disables this warning. Thiago> Anyway, the PYTHON_CFLAGS are only used to compile files under the Thiago> python/ subdir. I just checked here and varobj.c isn't compiled with it. I suppose we should widen this to any file that includes python-internal.h. Or, rework things so that varobj.c does not have to include that file. Given that these flags that are needed by python headers are basically bug workarounds, it might be nice to try to limit the fallout. Tom