From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BC9EC3858C50; Sun, 30 Apr 2023 06:08:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BC9EC3858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1682834897; bh=32xpxI8gy6OjmB+RYAq5y6STuTNDd7PytGrctg2Z8ok=; h=From:To:Subject:Date:From; b=dIO/TP489ntOlnSA0ufLcfODLtzm+OiP2gwtDL6nwwvN+zECPOdbt/b46wKohZCuD cRLdATQnab6fXyEijaaymr198WxF7ksXI3UqceD0foHgr9T2I5OQX8xvxOv7Jspw2w NA6piKohr0kWziAXuoQS/hzSlqoqge6H2OP3iC40= From: "agentzh at gmail dot com" 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: tapsets X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agentzh at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30407 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/mas= ter, origin/HEAD) Author: Frank Ch. Eigler Date: Fri Apr 28 12:07:15 2023 -0400 NEWS++ ``` --=20 You are receiving this mail because: You are the assignee for the bug.=