From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-42027-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 2177 invoked by alias); 23 Apr 2013 18:08:34 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 2168 invoked by uid 89); 23 Apr 2013 18:08:34 -0000
X-Spam-SWARE-Status: No, score=-7.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28)    by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 23 Apr 2013 18:08:33 +0000
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r3NI8W8s004052	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);	Tue, 23 Apr 2013 14:08:32 -0400
Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1])	by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r3NI8UUM016833	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);	Tue, 23 Apr 2013 14:08:31 -0400
From: Tom Tromey <tromey@redhat.com>
To: "Elmenthaler\, Jens" <JENS.ELMENTHALER@advantest.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb bug or corrupt dwarf info?
References: <CEA8125BCE884349929B204B961E547128E06D8F@DEBOSVPEX001.ent.rt.verigy.net>	<87ip4bb6d1.fsf@fleche.redhat.com>	<CEA8125BCE884349929B204B961E547128E2D92E@DEBOSVPEX001.ent.rt.verigy.net>
Date: Tue, 23 Apr 2013 18:08:00 -0000
In-Reply-To: <CEA8125BCE884349929B204B961E547128E2D92E@DEBOSVPEX001.ent.rt.verigy.net>	(Jens Elmenthaler's message of "Thu, 18 Apr 2013 11:47:18 +0000")
Message-ID: <87obd5p1b5.fsf@fleche.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-SW-Source: 2013-04/txt/msg00062.txt.bz2

>>>>> "Jens" == Elmenthaler, Jens <JENS.ELMENTHALER@advantest.com> writes:

Jens> I added the following code to read_lexical_block_scope(), right
Jens> behind the processing of the children. In case the test is
Jens> positive, I "repair" the affected die_info's:

Jens>   struct die_info *sibling = sibling_die(die);
Jens>   if (sibling && (sibling->tag == DW_TAG_lexical_block))

Is it valid to assume that the two DIEs will be siblings?
Maybe that is the only way the bug can manifest.  You may want to check.

Jens> First tests seem promising, so is there any reason I shouldn't do this?

It seems like it could work ok.

Tom