public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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 14:34:48 +0000	[thread overview]
Message-ID: <bug-27984-6586-63ugBMnswM@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 #5 from William Cohen <wcohen at redhat dot com> ---
There is something odd happening in the mapping of the address back to a name. 
The address 0x61b70 appears to be the correct address for
tls_process_client_hello according to nm, but the search is mapping it to
instance state_machine.part.0, 0000000000051540.  Systemtap keys off the
".part." in the name to determine that it is an inlined function.  Due to the
name mix up in this case systemtap incorrectly determines 0x61b70 is a
partially-inlined function.

Have been using rr (rr-project.org) to work backwards and determine why
dwfl_module_addrinfo is returning the wrong symbol name. The actual selection
of "state_machine.part.0" is occurs in the last line of 
__libdwfl_getsym@dwarf_module_getsym.c:197.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2021-07-15 14:34 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 [this message]
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-63ugBMnswM@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).