From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26184] fullpath_struct_file does not handle struct dentry on 5.6.19-300.fc32.x86_64
Date: Tue, 22 Mar 2022 18:15:17 +0000 [thread overview]
Message-ID: <bug-26184-6586-LbmUXbP9sZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26184-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26184
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |wcohen at redhat dot com
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
This looks to be fixed by commit 3739d47c4cc427ce4818d884f429a3efa85c38ae
$ uname -a
Linux fedora32 5.11.22-100.fc32.x86_64 #1 SMP Wed May 19 18:58:25 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
$ sudo ../install/bin/stap -v -c /bin/false -e 'probe process.begin {
printf("%s", fullpath_struct_file(task_current(), current_exe_file())); exit();
}'
Pass 1: parsed user script and 482 library scripts using
330920virt/94860res/17164shr/77736data kb, in 110usr/30sys/145real ms.
Pass 2: analyzed script: 1 probe, 31 functions, 2 embeds, 0 globals using
492840virt/258500res/18852shr/239656data kb, in 1190usr/390sys/1602real ms.
Pass 3: translated to C into
"/tmp/stapZC6Ukv/stap_e758ceff27992605c6d07aaf7c9484a8_14053_src.c" using
492840virt/258628res/18980shr/239656data kb, in 0usr/60sys/69real ms.
Pass 4: compiled C into "stap_e758ceff27992605c6d07aaf7c9484a8_14053.ko" in
11480usr/1640sys/13231real ms.
Pass 5: starting run.
WARNING: Child process exited with status 1
/home/wcohen/systemtap_write/install/libexec/systemtap/stapioWARNING:
/home/wcohen/systemtap_write/install/bin/staprun exited with status: 1
Pass 5: run completed in 10usr/30sys/301real ms.
Pass 5: run failed. [man error::pass5]
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-03-22 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 21:26 [Bug tapsets/26184] New: " guillaume at morinfr dot org
2021-05-26 22:06 ` [Bug tapsets/26184] " guillaume at morinfr dot org
2022-03-22 18:15 ` wcohen at redhat dot com [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-13 6:48 Craig Ringer
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-26184-6586-LbmUXbP9sZ@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).