From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10726] New: Getting wrong scope for inlined function
Date: Fri, 02 Oct 2009 21:38:00 -0000 [thread overview]
Message-ID: <20091002213805.10726.mjw@redhat.com> (raw)
In the following example (which doesn't currently work because we don't support
DW_AT_const_value yet), we get the scope wrong when probing func (inlined into
main with gcc -O2):
#include "sdt.h"
struct foo
{
const int i;
const long j;
};
typedef struct foo fooer;
static volatile int foobar;
static int bar (const int i, const long j)
{
return i * j;
}
static int func (int (*f) ())
{
const fooer baz = { .i = 2, .j = 21 };
STAP_PROBE (test, constvalues);
return f(baz.i, baz.j);
}
int
main (int argc, char *argv[], char *envp[])
{
return func (&bar) - 42;
}
This is because of the following logic in dwarf_var_expanding_visitor::getscopes:
// If the address is at the beginning of the scope_die, we can do a fast
// getscopes from there. Otherwise we need to look it up by address.
Dwarf_Addr entrypc;
if (q.dw.die_entrypc(scope_die, &entrypc) && entrypc == addr)
scopes = q.dw.getscopes(scope_die);
else
scopes = q.dw.getscopes(addr);
--
Summary: Getting wrong scope for inlined function
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10726
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-10-02 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 21:38 mjw at redhat dot com [this message]
2009-10-02 21:54 ` [Bug translator/10726] " jistone at redhat dot com
2009-10-02 21:57 ` jistone at redhat dot com
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=20091002213805.10726.mjw@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--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).