From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4865 invoked by alias); 12 Feb 2013 19:25:06 -0000 Received: (qmail 4788 invoked by uid 22791); 12 Feb 2013 19:25:04 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Feb 2013 19:24:56 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r1CJOstk031893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Feb 2013 14:24:54 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r1CJOrEH028580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 12 Feb 2013 14:24:54 -0500 From: Tom Tromey To: Kai Schuetz Cc: "gdb\@sourceware.org" Subject: Re: Crash triggered by DWARF debug info: Any ideas ? References: <15151570812B8041A31A98C098B7E75104291D@DE02WEMBX2.internal.synopsys.com> Date: Tue, 12 Feb 2013 19:25:00 -0000 In-Reply-To: <15151570812B8041A31A98C098B7E75104291D@DE02WEMBX2.internal.synopsys.com> (Kai Schuetz's message of "Fri, 8 Feb 2013 16:38:29 +0000") Message-ID: <87liatnxmi.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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/msg00033.txt.bz2 >>>>> "Kai" == Kai Schuetz writes: 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 for Kai> each compilation unit, consisting of name, producer, comp_dir, low_pc, Kai> high_pc and stmt_list. The .debug_line section contains line Kai> statements for the compilation units. [...] Kai> Any idea what to hunt for ? 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. Tom