From: Tom Tromey <tromey@redhat.com>
To: Tomasz Grobelny <tomasz@grobelny.oswiecenia.net>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>, <gdb@sourceware.org>
Subject: Re: sun compiler and gdb
Date: Wed, 09 May 2012 20:31:00 -0000 [thread overview]
Message-ID: <871umtrtab.fsf@fleche.redhat.com> (raw)
In-Reply-To: <543302446b67dbf68e8cedb69a197d77@192.168.5.248> (Tomasz Grobelny's message of "Thu, 03 May 2012 15:59:47 +0200")
>>>>> "Tomasz" == Tomasz Grobelny <tomasz@grobelny.oswiecenia.net> writes:
tomasz> Die: DW_TAG_<unknown> (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_<unknown>, which isn't very helpful... but
presumably the platform DWARF dumper would do better.
Tom
next prev parent reply other threads:[~2012-05-09 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 3:23 Tomasz Grobelny
2012-05-03 6:50 ` Sergio Durigan Junior
2012-05-03 14:00 ` Tomasz Grobelny
2012-05-09 20:31 ` Tom Tromey [this message]
2012-05-09 22:58 ` Tomasz Grobelny
2012-05-09 23:23 ` Tomasz Grobelny
2012-05-10 13:34 ` Tom Tromey
2012-05-10 16:38 ` Tomasz Grobelny
2012-05-10 17:38 ` Tomasz Grobelny
2012-05-10 20:34 ` Tom Tromey
2012-05-10 20:39 ` Tom Tromey
2012-05-10 22:08 ` Tomasz Grobelny
2012-05-11 16:21 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871umtrtab.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tomasz@grobelny.oswiecenia.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox