From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28835 invoked by alias); 9 May 2012 20:31:23 -0000 Received: (qmail 28826 invoked by uid 22791); 9 May 2012 20:31:21 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD 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; Wed, 09 May 2012 20:30:57 +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 q49KUsHl003833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 May 2012 16:30:55 -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 q49KUqxS023513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 May 2012 16:30:53 -0400 From: Tom Tromey To: Tomasz Grobelny Cc: Sergio Durigan Junior , Subject: Re: sun compiler and gdb References: <25b0084e43f4d35410c8dff55a3be61d@192.168.5.248> <543302446b67dbf68e8cedb69a197d77@192.168.5.248> Date: Wed, 09 May 2012 20:31:00 -0000 In-Reply-To: <543302446b67dbf68e8cedb69a197d77@192.168.5.248> (Tomasz Grobelny's message of "Thu, 03 May 2012 15:59:47 +0200") Message-ID: <871umtrtab.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (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: 2012-05/txt/msg00033.txt.bz2 >>>>> "Tomasz" == Tomasz Grobelny writes: tomasz> Die: DW_TAG_ (abbrev 8, offset 0x199) [...] Tomasz> Dwarf Error: Cannot find type of die [in module /login/sg209371/a.out] Tomasz> This time this is gdb 7.0.1. Tomasz> The question is indeed whether the issue is on compiler side or Tomasz> gdb side. The comments from the link you mentioned are from Tomasz> 2007, I would think that Oracle is capable of fixing a bug in 5 Tomasz> years... Also the dwarfdump shows some sensible information Tomasz> (some symbols, names of the source files). This kind of question can't be answered without more information. It could be a compiler bug, or a gdb bug, or a disagreement about the interpretation of DWARF. If you have a small test case, a dump of the DWARF information might prove helpful. If you only have a large test case, then something more selective could help. For example, in the above you could examine the DWARF for DIE 0x199. gdb just says DW_TAG_, which isn't very helpful... but presumably the platform DWARF dumper would do better. Tom