From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/27984] stap skipping partially-inlined instance, but it is not inline function actually
Date: Thu, 15 Jul 2021 15:28:36 +0000 [thread overview]
Message-ID: <bug-27984-6586-T824YOJXjN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27984-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27984
--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
The dwf_module_addrinfo lookup is not working. Any partially-inlined functions
in the code might cause random exclusions of valid functions as observed. Added
the following diagnostic print to see what dwfl_module_addrinfo() was
returning for each of the tests to verify it matched up with the expected
function name:
diff --git a/tapsets.cxx b/tapsets.cxx
index 20e0cb68f..9d4fd7389 100644
--- a/tapsets.cxx
+++ b/tapsets.cxx
@@ -2283,6 +2283,9 @@ query_dwarf_func (Dwarf_Die * func, dwarf_query * q)
const char *name = dwfl_module_addrinfo (q->dw.module, entrypc,
&off, &sym, NULL, NULL,
NULL);
+ if (q->sess.verbose>2)
+ clog << _F("%s = dwfl_module_addrinfo(%p)\n",
+ name, (void*)entrypc);
if (name != NULL && strstr(name, ".part.") != NULL)
{
if (q->sess.verbose>2)
Then ran to see what were the results for the program having the issues:
~/research/profiling/systemtap_write/install/stap
--sysroot=/tmp/stap-job1/sysroot -vvv -L
'process("/usr/local/openresty/openssl/lib/libssl.so.1.1").function("*").call'
>& detailed_funct_entry.log
Lots of places didn't find an entry at all:
selected function BIO_new_ssl
(null) = dwfl_module_addrinfo(0x1f760)
selected function BIO_new_ssl_connect
(null) = dwfl_module_addrinfo(0x1f7e0)
selected function ssl_puts
(null) = dwfl_module_addrinfo(0x1ed10)
selected function ssl_new
(null) = dwfl_module_addrinfo(0x1ed40)
Other places different name return than expected:
selected function ssl3_handshake_write
_init = dwfl_module_addrinfo(0x2d000)
selected function ssl3_ctrl
ssl_new = dwfl_module_addrinfo(0x2ed90)
selected function ssl3_send_alert
dtls1_start_timer = dwfl_module_addrinfo(0x2fe00)
selected function ssl3_do_change_cipher_spec
dtls1_clear = dwfl_module_addrinfo(0x2fd50)
selected function ssl3_dispatch_alert
dtls1_get_timeout = dwfl_module_addrinfo(0x2ff00)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-07-15 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 2:26 [Bug translator/27984] New: " zhuizhuhaomeng at gmail dot com
2021-07-14 19:48 ` [Bug translator/27984] " wcohen at redhat dot com
2021-07-14 20:37 ` wcohen at redhat dot com
2021-07-15 0:39 ` lijunlong at openresty dot com
2021-07-15 1:37 ` lijunlong at openresty dot com
2021-07-15 14:34 ` wcohen at redhat dot com
2021-07-15 15:28 ` wcohen at redhat dot com [this message]
2021-07-15 16:22 ` wcohen at redhat dot com
2021-07-16 14:49 ` wcohen at redhat dot com
2021-07-16 18:39 ` wcohen at redhat dot com
2021-07-16 19:07 ` mark at klomp dot org
2021-07-17 0:25 ` lijunlong at openresty dot com
2021-07-17 22:05 ` wcohen 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-27984-6586-T824YOJXjN@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).