From: "zhuizhuhaomeng at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/27984] New: stap skipping partially-inlined instance, but it is not inline function actually
Date: Wed, 16 Jun 2021 02:26:44 +0000 [thread overview]
Message-ID: <bug-27984-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27984
Bug ID: 27984
Summary: stap skipping partially-inlined instance, but it is
not inline function actually
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: zhuizhuhaomeng at gmail dot com
Target Milestone: ---
Created attachment 13495
--> https://sourceware.org/bugzilla/attachment.cgi?id=13495&action=edit
the object file of libssl.so
The stap script:
probe
process("/usr/local/openresty/openssl/lib/libssl.so.1.1").function("tls_process_client_hello")
{
var_pid = pid();
printf("%ld\n", var_pid);
}
The build steps:
time /usr/bin/stap --sysroot=/tmp/stap-job1/sysroot -vvvvv \
-p2 \
-d "/usr/local/openresty/openssl/lib/libssl.so.1.1" --disable-cache \
"test.stp"
how to reproduce it:
download the attachment, and decompress to /tmp director.
enter into the /tmp/stap-job1 direcotry and run sh make.sh.
dwarf_builder::build for
/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1
parse 'tls_process_client_hello', func 'tls_process_client_hello'
pattern '/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1'
matches module
'/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1'
focused on module
'/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1' =
[0x10000-0xa59b0, bias 0 file
/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1 ELF
machine |x86_64 (code 62)
focused on module
'/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1'
module function cache
/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1 size 1785
module function cache
/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1 hit
tls_process_client_hello
selected function tls_process_client_hello
skipping partially-inlined instance state_machine.part.0 at 0x61b70
suggesting 1898 dwarf functions from modules:
/tmp/stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1
semantic error: while resolving probe point: identifier 'process' at
test.stp:2:7
thrown from: elaborate.cxx:1067
source: probe
process("/usr/local/openresty/openssl/lib/libssl.so.1.1").function("tls_process_client_hello")
{
^
semantic error: while resolving probe point: identifier 'process' at :2:7
thrown from: elaborate.cxx:1067
source: probe
process("/usr/local/openresty/openssl/lib/libssl.so.1.1").function("tls_process_client_hello")
{
^
semantic error: no match (similar functions: tls_process_client_hello,
tls_post_process_client_hello, tls_process_server_hello,
tls_early_post_process_client_hello, tls_process_cert_verify)
thrown from: tapsets.cxx:8883
deleting module_cache
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-06-16 2:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 2:26 zhuizhuhaomeng at gmail dot com [this message]
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
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@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).