From: Jan Blunck <jblunck@suse.de>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: [BUG?] semantic error: failed to retrieve location attribute for local
Date: Tue, 05 Dec 2006 17:20:00 -0000 [thread overview]
Message-ID: <20061205113428.GC10309@hasse.suse.de> (raw)
In-Reply-To: <y0mr6vfbpp4.fsf@ton.toronto.redhat.com>
On Mon, Dec 04, Frank Ch. Eigler wrote:
> > The full error message is as follows:
> > [...]
> > querying entrypc c0170197 of instance of inline 'real_lookup'
> > probe real_lookup@fs/namei.c:447 kernel section=.text pc=0xc0170197
> > finding location for local 'parent' near address c0170197, module bias 0
> > finding location for local 'name' near address c0170197, module bias 0
> > [...]
> > semantic error: failed to retrieve location attribute for local 'name'
> > (dieoffset: 85127198053): identifier '$name' at real_lookup.stp:9:20
> > [...]
> > Is this a bug?
>
> Problems such as this tend to be limitations of gcc debugging
> information quality. One frequently-hit bug is that few actual
> parameters get proper debugging information emitted, even if they are
> used by the inlined function body.
This is a major problem. A lot of interesting code is inlined in the
kernel. Any plans/ideas how to fix this issue?
But the debuginfo is emitted AFAICS, isn't it?
<1><6dd453>: Abbrev Number: 63 (DW_TAG_subprogram)
DW_AT_sibling : <6dd4b5>
DW_AT_name : (indirect string, offset: 0x38365): real_lookup
DW_AT_decl_file : 1
DW_AT_decl_line : 447
DW_AT_prototyped : 1
DW_AT_type : <6d4e44>
DW_AT_inline : 1 (inlined)
<2><6dd465>: Abbrev Number: 61 (DW_TAG_formal_parameter)
DW_AT_name : (indirect string, offset: 0x8bfef): parent
DW_AT_decl_file : 1
DW_AT_decl_line : 446
DW_AT_type : <6d4e44>
<2><6dd471>: Abbrev Number: 61 (DW_TAG_formal_parameter)
DW_AT_name : (indirect string, offset: 0x43b44): name
DW_AT_decl_file : 1
DW_AT_decl_line : 446
DW_AT_type : <6d7bc9>
<2><6dd47d>: Abbrev Number: 50 (DW_TAG_formal_parameter)
DW_AT_name : nd
DW_AT_decl_file : 1
DW_AT_decl_line : 446
DW_AT_type : <6d7b2b>
<2><6dd488>: Abbrev Number: 51 (DW_TAG_variable)
DW_AT_name : (indirect string, offset: 0x38552): result
DW_AT_decl_file : 1
DW_AT_decl_line : 448
DW_AT_type : <6d4e44>
<2><6dd494>: Abbrev Number: 64 (DW_TAG_variable)
DW_AT_name : dir
DW_AT_decl_file : 1
DW_AT_decl_line : 449
DW_AT_type : <6d7851>
<2><6dd4a0>: Abbrev Number: 65 (DW_TAG_lexical_block)
DW_AT_sibling : <6dd4b3>
<3><6dd4a5>: Abbrev Number: 51 (DW_TAG_variable)
DW_AT_name : (indirect string, offset: 0x211b): dentry
DW_AT_decl_file : 1
DW_AT_decl_line : 468
DW_AT_type : <6d4e44>
<3><6dd4b1>: Abbrev Number: 58 (DW_TAG_lexical_block)
<2><6dd4b3>: Abbrev Number: 58 (DW_TAG_lexical_block)
next prev parent reply other threads:[~2006-12-05 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 16:18 Jan Blunck
2006-12-04 16:27 ` Frank Ch. Eigler
2006-12-05 17:20 ` Jan Blunck [this message]
2006-12-06 22:32 ` Frank Ch. Eigler
2006-12-07 16:53 ` Jan Blunck
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=20061205113428.GC10309@hasse.suse.de \
--to=jblunck@suse.de \
--cc=fche@redhat.com \
--cc=systemtap@sources.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).