From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4438 invoked by alias); 6 Aug 2008 05:44:58 -0000 Received: (qmail 4429 invoked by uid 22791); 6 Aug 2008 05:44:57 -0000 X-Spam-Check-By: sourceware.org Received: from igw3.br.ibm.com (HELO igw3.br.ibm.com) (32.104.18.26) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Aug 2008 05:44:03 +0000 Received: from mailhub1.br.ibm.com (unknown [9.18.232.109]) by igw3.br.ibm.com (Postfix) with ESMTP id D5E49390045 for ; Wed, 6 Aug 2008 02:24:40 -0300 (BRST) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m765i1oK2113822 for ; Wed, 6 Aug 2008 02:44:01 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m765htci027403 for ; Wed, 6 Aug 2008 02:43:55 -0300 Received: from [9.8.13.235] ([9.8.13.235]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m765htQS027396; Wed, 6 Aug 2008 02:43:55 -0300 Subject: Re: gdb plugin status? From: Thiago Jung Bauermann To: tromey@redhat.com 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> Content-Type: text/plain Date: Wed, 06 Aug 2008 05:44:00 -0000 Message-Id: <1218001435.4534.60.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/msg00090.txt.bz2 On Tue, 2008-08-05 at 22:39 -0600, Tom Tromey wrote: > >>>>> "Thiago" == Thiago Jung Bauermann writes: > >> On Tue, 2008-08-05 at 15:53 -0700, Neo Jia wrote: > >> cc1: warnings being treated as errors > >> varobj.c: In function 'update_dynamic_varobj_children': > >> varobj.c:932: warning: dereferencing type-punned pointer will break > >> strict-aliasing rules > > Thiago> I don't see that error here. I think we are using different versions of > Thiago> gcc. I'm using 4.3.1. > > FWIW, my build uses -fno-strict-aliasing, which disables this warning. > I think this comes from python-config. It's more accurate to say that its use was inspired by python-config, since we don't actually call the utility. :-) Anyway, the PYTHON_CFLAGS are only used to compile files under the python/ subdir. I just checked here and varobj.c isn't compiled with it. -- []'s Thiago Jung Bauermann IBM Linux Technology Center