From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/30407] New: Tapset function print_ubacktrace_fileline() no longer works on kernel 6.2
Date: Sun, 30 Apr 2023 06:08:17 +0000 [thread overview]
Message-ID: <bug-30407-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30407
Bug ID: 30407
Summary: Tapset function print_ubacktrace_fileline() no longer
works on kernel 6.2
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
I've noted that the standard tapset function `print_ubacktrace_fileline()` no
longer works on the latest 6.2.12 kernel of fedora 36 x86_64.
To reproduce the problem, let's use the following minimal C program as the
target:
```
int main(void) {
return 0;
}
```
We name it `a.c`.
Then compile it with debug symbols:
```
gcc -g a.c
```
It generates the binary program ./a.out.
Now run the following stap oneliner:
```
$ /opt/stap/bin/stap -c ./a.out --ldd -e 'probe process.function("main") {
print_ubacktrace_fileline() }'
0x40110a : main+0x4/0xe [/tmp/a.out]
0x7f896e867510 : __libc_start_call_main+0x80/0xb0 [/usr/lib64/libc.so.6]
0x7f896e8675c9 : __libc_start_main@GLIBC_2.2.5+0x89/0x150
[/usr/lib64/libc.so.6]
0x401045 : _start+0x25/0x30 [/tmp/a.out]
```
We can see there are no source file names or line numbers.
For comparison, let's run the same example on an older kernel (5.0.16):
```
$ /opt/stap/bin/stap -c ./a.out --ldd -e 'probe process.function("main") {
print_ubacktrace_fileline() }'
0x40049a : main+0x4/0x1a at /tmp/a.c:2 [/tmp/a.out]
0x7fbc6289011b : __libc_start_main+0xeb/0x1c0 [/usr/lib64/libc-2.27.so]
0x4003da : _start+0x2a/0x30 [/tmp/a.out]
```
It works on this older kernel as expected.
I'm using the latest master branch of the upstream systemtap repo:
```
commit 418f0a45ca4473491385b5c7eef777607bbdb3b7 (HEAD -> master, origin/master,
origin/HEAD)
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Fri Apr 28 12:07:15 2023 -0400
NEWS++
```
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-04-30 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 6:08 agentzh at gmail dot com [this message]
2023-05-02 22:29 ` [Bug tapsets/30407] " agentzh at gmail dot com
2023-05-02 22:32 ` [Bug tapsets/30407] Tapset function print_ubacktrace_fileline() no longer works on kernel 6.2/6.1 agentzh at gmail dot com
2023-06-08 14:27 ` mcermak at redhat dot com
2023-06-08 14:39 ` [Bug tapsets/30407] Tapset function print_ubacktrace_fileline() no longer works with DWARF5 mcermak at redhat dot com
2023-07-12 14:47 ` wcohen at redhat dot com
2023-07-14 15:25 ` mcermak at redhat dot com
2023-07-26 14:40 ` mark at klomp dot org
2023-10-10 9:14 ` mcermak at redhat dot com
2023-10-10 9:14 ` mcermak 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-30407-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).