From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25549] Systemtap unable to find many probe points available in code compiled with LTO enable
Date: Tue, 05 May 2020 15:41:20 +0000 [thread overview]
Message-ID: <bug-25549-6586-YB4pBVkPWU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25549-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25549
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Systemtap's logic to determine whether a function should be added to the list
of filtered_functions in a query is getting confused by the where the
information about the function entry address is placed for the LTO binaries.
query_dwarf_func (Dwarf_Die * func, dwarf_query * q) seems to miss the fact
that function entry address is stored in another DIE and never pushs the
function to the list. Shows the DIEs extracted from the reproducer by dwgrep:
$ dwgrep pr25549.lto -e 'entry ?TAG_subprogram'
[36e] subprogram
external true
name "main"
decl_file "/home/wcohen/rpmbuild/BUILDROOT/pr25549.cxx"
decl_line 3
decl_column 5
type [de] base_type
sibling [397] pointer_type
[2e] subprogram
abstract_origin [36e] subprogram
low_pc 0x401040
high_pc 21
frame_base 0..0xffffffffffffffff:0 call_frame_cfa
GNU_all_call_sites true
sibling [7f] subprogram
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-05 15:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 15:40 [Bug translator/25549] New: " wcohen at redhat dot com
2020-05-01 18:31 ` [Bug translator/25549] " wcohen at redhat dot com
2020-05-04 20:18 ` wcohen at redhat dot com
2020-05-05 15:41 ` wcohen at redhat dot com [this message]
2020-05-05 20:49 ` woodard at redhat dot com
2020-05-07 2:06 ` fche at redhat dot com
2020-05-07 3:26 ` mark at klomp dot org
2020-05-07 10:27 ` fche at redhat dot com
2020-05-07 10:28 ` fche at redhat dot com
2020-05-07 11:36 ` mark at klomp dot org
2020-05-07 13:58 ` wcohen at redhat dot com
2020-05-07 17:55 ` wcohen at redhat dot com
2020-05-08 10:15 ` mark at klomp dot org
2020-05-08 14:02 ` wcohen at redhat dot com
2020-05-08 17:25 ` mark at klomp dot org
2020-05-08 20:07 ` wcohen at redhat dot com
2020-07-10 3:00 ` fche 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-25549-6586-YB4pBVkPWU@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).