From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/17966] @defined always returns true in return probes
Date: Thu, 12 Feb 2015 22:08:00 -0000 [thread overview]
Message-ID: <bug-17966-6586-afnvZzR0u5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17966-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17966
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|systemtap at sourceware dot org |jistone at redhat dot com
--- Comment #1 from Josh Stone <jistone at redhat dot com> ---
I did suggest that's what going on, but it appears more subtle when I look
closer.
If I try process("bash").function("main").return, it gets this error. I don't
have debuginfo installed for bash.
If I try process("stap").function("main").return, it works as expected. I do
have debuginfo for my local stap.
In dwarf_var_expanding_visitor::visit_target_symbol, we have:
// Everything else (pretty-printed vars, and context vars) require a
// scope_die in which to search for them. If we don't have that, just
// leave it unresolved; we'll produce an error later on.
if (null_die(scope_die))
{
provide(e);
return;
}
The case without debuginfo will hit this and return without error, leaving
@defined undecided for the moment. The case with debuginfo will get past this,
set an error on e directly, and cause @defined to be 0 right away, as desired.
So I need to figure out why the delayed case doesn't fix @defined later...
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2015-02-12 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:32 [Bug translator/17966] New: " aram.h at mgk dot ro
2015-02-12 21:33 ` [Bug translator/17966] " aram.h at mgk dot ro
2015-02-12 22:08 ` jistone at redhat dot com [this message]
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=bug-17966-6586-afnvZzR0u5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).