From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 564 invoked by alias); 6 Aug 2008 20:46:00 -0000 Received: (qmail 554 invoked by uid 22791); 6 Aug 2008 20:45:59 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Aug 2008 20:45:15 +0000 Received: from mailhub1.br.ibm.com (mailhub1 [9.18.232.109]) by igw2.br.ibm.com (Postfix) with ESMTP id B0CB217F67F for ; Wed, 6 Aug 2008 17:31:17 -0300 (BRT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m76Khtqj1548782 for ; Wed, 6 Aug 2008 17:44:17 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m76KhmMY007987 for ; Wed, 6 Aug 2008 17:43:49 -0300 Received: from [9.8.1.201] ([9.8.1.201]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m76KhlB2007755; Wed, 6 Aug 2008 17:43:47 -0300 Subject: Re: gdb plugin status? From: Thiago Jung Bauermann To: Tom Tromey Cc: Neo Jia , gdb ml In-Reply-To: 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> Content-Type: text/plain Date: Wed, 06 Aug 2008 20:46:00 -0000 Message-Id: <1218055425.6617.5.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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/msg00115.txt.bz2 On Wed, 2008-08-06 at 14:36 -0600, Tom Tromey wrote: > >>>>> "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. Right, nothing outside python/ is supposed to include python-internal.h (that's why I put the -internal suffix :-) ). varobj.c does it at the moment because we didn't get around to cleanup the MI python patch yet. -- []'s Thiago Jung Bauermann IBM Linux Technology Center