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: Mon, 04 May 2020 20:18:29 +0000 [thread overview]
Message-ID: <bug-25549-6586-6pltbhBMHm@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 #2 from William Cohen <wcohen at redhat dot com> ---
The eu-readelf --debug-dump=info output of the non-lto and lto versions of the
reproducer show one difference that is maybe be tripping up systemtap.
On non-lto:
[ 2f1] subprogram abbrev: 16
external (flag_present) yes
name (strp) "main"
decl_file (data1) pr25549.cxx (1)
decl_line (data1) 3
decl_column (data1) 5
type (ref4) [ 61]
low_pc (addr) 0x0000000000401040 <main>
high_pc (data8) 21 (0x0000000000401055
<.annobin_static_reloc.c_end.hot>)
frame_base (exprloc)
[ 0] call_frame_cfa
GNU_all_call_sites (flag_present) yes
sibling (ref4) [ 357]
on lto one, no low_pc, high_pc:
[ 36e] subprogram abbrev: 16
external (flag_present) yes
name (strp) "main"
decl_file (data1) pr25549.cxx (7)
decl_line (data1) 3
decl_column (data1) 5
type (ref4) [ de]
sibling (ref4) [ 397]
Comparing the execution of the working non-LTO and the non-working LTO it
looks like the following line tapset.cxx:2403 returns nothing to iterate over,
so no lines are reported for the LTO version of the code :
auto bfis = q->filtered_all();
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-04 20:18 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 [this message]
2020-05-05 15:41 ` wcohen at redhat dot com
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-6pltbhBMHm@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).