From: "brolley at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13143] process.library("libfoo.so").function(ADDRESS).call/return fail to resolve
Date: Tue, 30 Aug 2011 19:52:00 -0000 [thread overview]
Message-ID: <bug-13143-6586-uAtifzYK5w@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13143-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13143
--- Comment #4 from Dave Brolley <brolley at redhat dot com> 2011-08-30 19:51:29 UTC ---
(In reply to comment #2)
> Looks like it is working as designed.
>
> probe process ("libfoo.so").library("libfoo.so").function(0x55e).call
> maps to and seems to behave identical to:
> probe process ("libfoo.so").function(0x55e).call
>
> query_addr has this check.
> if ((tag == DW_TAG_subprogram && !q->has_inline) ||
> (tag == DW_TAG_inlined_subroutine &&
> !q->has_call && !q->has_return))
> which in the above case is checking
> tag == DW_TAG_inlined_subroutine
> q->has_call == true
>
> and thus it fails.
>
> For the case where a probe is added to libfoofunc then the check becomes
> tag == DW_TAG_subprogram
> q->has_inline == true
So are you saying that it's not resolving because the function libfoofunc was
inlined (because it was empty)?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-08-30 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 15:02 [Bug translator/13143] New: " brolley at redhat dot com
2011-08-30 15:17 ` [Bug translator/13143] " brolley at redhat dot com
2011-08-30 19:41 ` scox at redhat dot com
2011-08-30 19:43 ` scox at redhat dot com
2011-08-30 19:52 ` brolley at redhat dot com [this message]
2011-09-06 16:37 ` brolley 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=bug-13143-6586-uAtifzYK5w@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).