From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2143 invoked by alias); 8 Sep 2009 20:41:54 -0000 Received: (qmail 2100 invoked by uid 22791); 8 Sep 2009 20:41:53 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 Sep 2009 20:41:45 +0000 Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id n88Kfgdv010057 for ; Tue, 8 Sep 2009 21:41:42 +0100 Received: from yxe1 (yxe1.prod.google.com [10.190.2.1]) by wpaz5.hot.corp.google.com with ESMTP id n88KesY3006944 for ; Tue, 8 Sep 2009 13:41:40 -0700 Received: by yxe1 with SMTP id 1so2883404yxe.28 for ; Tue, 08 Sep 2009 13:41:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.80.7 with SMTP id d7mr17613558anb.43.1252442498132; Tue, 08 Sep 2009 13:41:38 -0700 (PDT) In-Reply-To: <000301ca309f$35d475d0$a17d6170$@u-strasbg.fr> References: <20090902164425.GR4379@adacore.com> <8ac60eac0909030854j21d514f9h5047a099a3eb3d80@mail.gmail.com> <000901ca2caf$947d50a0$bd77f1e0$@u-strasbg.fr> <8ac60eac0909030911j16860840p39a70be37576f88@mail.gmail.com> <001401ca2d49$29047160$7b0d5420$@u-strasbg.fr> <8ac60eac0909040807n14dc65b3yef693f69dd193e97@mail.gmail.com> <000c01ca2fcb$594cea80$0be6bf80$@u-strasbg.fr> <8ac60eac0909072137g41f7b1f8q2e9e1e6d6d161fc5@mail.gmail.com> <000301ca309f$35d475d0$a17d6170$@u-strasbg.fr> Date: Tue, 08 Sep 2009 20:41:00 -0000 Message-ID: <8ac60eac0909081341v1f36110fkfd5361a3aa6dc88b@mail.gmail.com> Subject: Re: [gdb-7.0 release] 2009-09-02 status and proposed plan From: Paul Pluzhnikov To: Pierre Muller Cc: gdb Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true 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: 2009-09/txt/msg00140.txt.bz2 Back on gdb@ list. On Tue, Sep 8, 2009 at 9:12 AM, Pierre Muller wrot= e: > > >> -----Message d'origine----- >> De=A0: Paul Pluzhnikov [mailto:ppluzhnikov@google.com] >> Envoy=E9=A0: Tuesday, September 08, 2009 6:37 AM >> =C0=A0: Pierre Muller >> Objet=A0: Re: [gdb-7.0 release] 2009-09-02 status and proposed plan >> >> Off-list. >> >> On Mon, Sep 7, 2009 at 7:56 AM, Pierre Muller >> wrote: >> >> > =A0[ 6] .SUNW_version VERNEED =A00000572c 00572c 000060 01 =A0 A =A05 = 3 =A04 >> > =A0[ 7] .SUNW_version VERDEF =A0 0000578c 00578c 000038 01 =A0 A =A05 = 2 =A04 >> > =A0[ 8] .SUNW_versym =A0VERSYM =A0 000057c4 0057c4 000148 02 =A0 A =A0= 4 0 =A04 >> >> AFAICT, above sections do *not* overlap, which means that there is a >> bug in my patch (I don't see it :-(, or something else went wrong. >> >> >> On Fri, Sep 4, 2009 at 3:19 AM, Pierre Muller >> >> wrote: >> >> >> >> > =A0I checked your patch and it does solve the problem. >> >> > Instead of a internal_error, I get a warning >> >> > about .SUNW_version and .SUNW_versym sections >> >> > between intertwined. >> >> Could you please send me the exact warning from patched GDB. > Here you are, > hope you can do something with it! > > (top-gdb) start > Temporary breakpoint 3 at 0x80c7074: file ../../src/gdb/gdb.c, line 28. > Starting program: /usr/local/src/gdbcvs/build/gdb/gdb > warning: Unexpected overlap between section `.SUNW_version' from `/usr/li= b/ld.so.1' [0xfefc378c, 0xfefc37ec) and section `.SUNW_versym' from `/usr/l= ib/ld.so.1' [0xfefc37c4, 0xfefc390c) > [Thread debugging using libthread_db enabled] > warning: Unexpected overlap between section `.SUNW_version' from `/usr/li= b/ld.so.1' [0xfefc378c, 0xfefc37ec) and section `.SUNW_versym' from `/usr/l= ib/ld.so.1' [0xfefc37c4, 0xfefc390c) > [New Thread 1 (LWP 1)] > [Switching to Thread 1 (LWP 1)] It seems pretty clear now that BFD (or something) is getting confused by the presence of two separate .SUNW_version sections. In particular, section #7 somehow acquired the size (0x60) from section #6, and that causes the warning. I'll go ahead and debug this today. Thanks, --=20 Paul Pluzhnikov