From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32766 invoked by alias); 6 Aug 2008 03:27:23 -0000 Received: (qmail 32755 invoked by uid 22791); 6 Aug 2008 03:27:22 -0000 X-Spam-Check-By: sourceware.org Received: from igw1.br.ibm.com (HELO igw1.br.ibm.com) (32.104.18.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Aug 2008 03:26:39 +0000 Received: from mailhub3.br.ibm.com (mailhub3 [9.18.232.110]) by igw1.br.ibm.com (Postfix) with ESMTP id 6F1FC32C2D9 for ; Tue, 5 Aug 2008 23:58:00 -0300 (BRT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m763QQCT4587668 for ; Wed, 6 Aug 2008 00:26:31 -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 m763QKLG004246 for ; Wed, 6 Aug 2008 00:26:20 -0300 Received: from [9.8.13.235] ([9.8.13.235]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m763QKOm003859; Wed, 6 Aug 2008 00:26:20 -0300 Subject: Re: gdb plugin status? From: Thiago Jung Bauermann To: Neo Jia Cc: gdb ml In-Reply-To: <5d649bdb0808051553g6ee22cbfr80cfa43cd56e870c@mail.gmail.com> 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> Content-Type: text/plain Date: Wed, 06 Aug 2008 03:27:00 -0000 Message-Id: <1217993159.4534.47.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/msg00084.txt.bz2 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 I don't see that error here. I think we are using different versions of gcc. I'm using 4.3.1. You can configure with --disable-werror to compile even with warnings. > BTW, how to pull the changes out? git pull doesn't work for this case? git pull should work. You can also try: $ git pull origin python-revisited:python-revisited -- []'s Thiago Jung Bauermann IBM Linux Technology Center