public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tomasz Grobelny <tomasz@grobelny.oswiecenia.net>
To: Tom Tromey <tromey@redhat.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>, <gdb@sourceware.org>
Subject: Re: sun compiler and gdb
Date: Thu, 10 May 2012 22:08:00 -0000	[thread overview]
Message-ID: <3a8ec212743662e9fb765b02c1845c90@192.168.5.248> (raw)
In-Reply-To: <87pqab93f8.fsf@fleche.redhat.com>

On Thu, 10 May 2012 14:39:07 -0600, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Tomasz" == Tomasz Grobelny <tomasz@grobelny.oswiecenia.net>
writes:
> 
> Tomasz> Reading symbols from
> /login/sg209371/gdbtest/a.out.sparc...expanding to
> Tomasz> full symbols...Die: DW_TAG_<unknown> (abbrev 9, offset 0x1bb)
> 
> You want DIE 0x1bb...
> 
> Tomasz>   parent at offset: 0x197
> 
> ... or perhaps 0x197 ...
> 
> Tomasz> With the relevant portion of dwarfdump looking like this:
> Tomasz> <2><  443>	DW_TAG_SUN_class_template
> 
> But this appears to be DIE 0x443.
> 
Actually it is DIE 443(dec) == 1bb(hex)
When you posted output from another dwarfdump version it took me a while
to figure out that one tool is giving numbers in hex and the other in dec.

> Tomasz> Shouldn't unknown tag just be ignored?
> 
> Yes, but I think what is happening is that you have one DIE which uses
> DW_AT_type to refer to another DIE, and gdb doesn't know what to do with
> the type DIE.
> 
Does the above comment about dec/hex values change your analysis here?

> Tomasz> I searched for other tags that might be compiler specific and
> Tomasz> here is the list:
> 
> Those are actually attributes; tags would be DW_TAG_something.
> 
Thanks for pointing that out - I am new to DWARF stuff and do not yet see
the difference between attribute, tag and die.

> Tomasz> Are any of these supported or (at least) explicitly ignored by
gdb?
> 
> AFAIK, no Sun extensions to DWARF are supported by gdb.
> Generally they should be ignored, but as you've seen, there are
> sometimes exceptions.  My impression is that this part of gdb is not
> heavily tested.
> 
I will have a look it they can somehow be removed...
-- 
Regards,
Tomasz Grobelny

  reply	other threads:[~2012-05-10 22:08 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
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 [this message]
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=3a8ec212743662e9fb765b02c1845c90@192.168.5.248 \
    --to=tomasz@grobelny.oswiecenia.net \
    --cc=gdb@sourceware.org \
    --cc=sergiodj@redhat.com \
    --cc=tromey@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).