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: Wed, 14 Jul 2021 19:48:51 +0000 [thread overview]
Message-ID: <bug-27984-6586-UmePAvBTsV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27984-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27984
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |wcohen at redhat dot com
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-07-14
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
What specific compiler and openssl source were used to create the reproducer?
If tls_process_client_hello is really a partially inlined function, then it
should be skipped and the probe be place in the inlined piece of
tls_process_client_hello. However, there doesn't seem to rest of the function
listed as a regular function (DW_TAG_subprogram) or inlined
(DW_TAG_inlined_subroutine) in the debuginfo,but there is a
DW_TAG_GNU_call_site:
$ llvm-dwarfdump --name=tls_process_client_hello
stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1
stap-job1/sysroot/usr/local/openresty/openssl/lib/libssl.so.1.1: file
format elf64-x86-64
0x001069fb: DW_TAG_subprogram
DW_AT_external (true)
DW_AT_name ("tls_process_client_hello")
DW_AT_decl_file
("/tmp/openssl-OpenSSL_1_1_1g/ssl/statem/statem_srvr.c")
DW_AT_decl_line (1383)
DW_AT_decl_column (0x14)
DW_AT_prototyped (true)
DW_AT_type (0x000ffac0 "MSG_PROCESS_RETURN")
DW_AT_low_pc (0x0000000000061b70)
DW_AT_high_pc (0x000000000006253e)
DW_AT_frame_base (DW_OP_call_frame_cfa)
DW_AT_GNU_all_call_sites (true)
DW_AT_sibling (0x001081b4)
0x001084cd: DW_TAG_GNU_call_site
DW_AT_low_pc (0x0000000000065195)
DW_AT_GNU_tail_call (true)
DW_AT_abstract_origin (0x001069fb "tls_process_client_hello")
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-07-14 19:48 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 ` wcohen at redhat dot com [this message]
2021-07-14 20:37 ` [Bug translator/27984] " 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-UmePAvBTsV@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).