From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29600 invoked by alias); 13 Feb 2013 11:45:19 -0000 Received: (qmail 29587 invoked by uid 22791); 13 Feb 2013 11:45:18 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from vaxjo.synopsys.com (HELO vaxjo.synopsys.com) (198.182.60.75) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 13 Feb 2013 11:45:15 +0000 Received: from mailhost.synopsys.com (unknown [10.9.202.240]) by vaxjo.synopsys.com (Postfix) with ESMTP id 92951E2F4; Wed, 13 Feb 2013 03:45:14 -0800 (PST) Received: from mailhost.synopsys.com (localhost [127.0.0.1]) by mailhost.synopsys.com (Postfix) with ESMTP id 815DEFC1; Wed, 13 Feb 2013 03:45:14 -0800 (PST) Received: from US01WXQAHTC1.internal.synopsys.com (us01wxqahtc1.internal.synopsys.com [10.12.238.230]) by mailhost.synopsys.com (Postfix) with ESMTP id 74E81FC0; Wed, 13 Feb 2013 03:45:14 -0800 (PST) Received: from DE02WEHTC1.internal.synopsys.com (10.225.19.83) by US01WXQAHTC1.internal.synopsys.com (10.12.238.230) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 13 Feb 2013 03:45:14 -0800 Received: from DE02WEMBX2.internal.synopsys.com ([fe80::e51d:dd29:ce50:4455]) by DE02WEHTC1.internal.synopsys.com ([::1]) with mapi id 14.02.0298.004; Wed, 13 Feb 2013 12:45:11 +0100 From: Kai Schuetz To: Tom Tromey CC: "gdb@sourceware.org" Subject: RE: Crash triggered by DWARF debug info: Any ideas ? Date: Wed, 13 Feb 2013 11:45:00 -0000 Message-ID: <15151570812B8041A31A98C098B7E751042EDC@DE02WEMBX2.internal.synopsys.com> References: <15151570812B8041A31A98C098B7E75104291D@DE02WEMBX2.internal.synopsys.com> <87liatnxmi.fsf@fleche.redhat.com> In-Reply-To: <87liatnxmi.fsf@fleche.redhat.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: 2013-02/txt/msg00045.txt.bz2 Hi Tom, > -----Original Message----- > From: Tom Tromey [mailto:tromey@redhat.com] > Sent: Tuesday, February 12, 2013 20:25 > To: Kai Schuetz > Cc: gdb@sourceware.org > Subject: Re: Crash triggered by DWARF debug info: Any ideas ? >=20 > >>>>> "Kai" =3D=3D Kai Schuetz writes: >=20 > Kai> I'm looking into some crash in gdb 7.5.1 in the DWARF reader. > Kai> The DWARF (v3) debug info in the case is pretty basic (it was > Kai> generated by the "ARM Assembler", version 4.0). > Kai> The .debug_info section just consists of a single debug info entry > Kai> for each compilation unit, consisting of name, producer, comp_dir, > Kai> low_pc, high_pc and stmt_list. The .debug_line section contains > Kai> line statements for the compilation units. > [...] > Kai> Any idea what to hunt for ? >=20 > I don't think there's an easy way to debug it. Offhand I don't know what= is > wrong. You might try having end_symtab_get_static_block always return a > block. It's easier to do this with a newer gdb, this area changed a bit. What is the relation of DWARF info and (static?) blocks ? I assume there should be one static block per compilation unit ? With "newer gdb" I assume you refer to one checked out CVS since 7.5.1 is t= he latest release ? Thanks, Kai