From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/27940] New: The /* pc=0x... */ is no longer printed by "stap -v -L 'kernel.function("*")'
Date: Tue, 01 Jun 2021 17:09:47 +0000 [thread overview]
Message-ID: <bug-27940-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27940
Bug ID: 27940
Summary: The /* pc=0x... */ is no longer printed by "stap -v -L
'kernel.function("*")'
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
When using a current checkout of systemtap from the git repository I found that
the following no longer included the pc address of the probe point:
$ ../install/bin/stap -v -L 'kernel.function("BTRFS_I")'
Pass 1: parsed user script and 792 library scripts using
3480940virt/3246072res/12984shr/3233236data kb, in 7720usr/700sys/8499real ms.
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231")
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231")
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231")
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231")
With the recently released systemtap-4.5 on fedora 34 see:
$ stap -v -L 'kernel.function("BTRFS_I")'
Pass 1: parsed user script and 791 library scripts using
3479644virt/3245148res/12412shr/3232604data kb, in 7840usr/660sys/8549real ms.
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231") /* pc=_stext+0x53a068 */
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231") /* pc=_stext+0x539ff8 */
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231") /* pc=_stext+0x539f83 */
kernel.function("BTRFS_I@fs/btrfs/btrfs_inode.h:231") /* pc=_stext+0x5373d3 */
...
Did a binary bisect and tracked the problem down to git commit
545535f8238fe2493dd7b2d415dfa12174284581:
Author: Timm Bäder <tbaeder@redhat.com> 2021-05-19 16:38:30
Committer: Aaron Merey <amerey@redhat.com> 2021-05-19 16:38:30
Parent: 0f4bd3219711e8918eac77c77a1de521832d3dbe (set2: Return this from
assignment operator)
Child: b3a3929751695310b93ff35f41e68775804cee00 (Fix -Wformat-nonliteral and
-Wformat warnings with clang)
Branches: master, remotes/origin/master
Follows: release-4.5
Precedes:
Fix -Woverloaded-virtual warnings when building with clang
Satisfy clang by removing option for non-nested signature printing from
implementations of printsig and declare derived_probe::printsig with
'override'.
Add function derived_probe::printsig_nonest to perform non-nested signature
printing.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-06-01 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 17:09 wcohen at redhat dot com [this message]
2021-06-03 22:38 ` [Bug translator/27940] " wcohen at redhat dot com
2021-06-04 19:50 ` fche at redhat dot com
2021-08-31 1:09 ` dichen 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-27940-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).