This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/23284] New: dmesg should identify the name of the stap script
- From: "serhei.public at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 13 Jun 2018 15:54:05 +0000
- Subject: [Bug runtime/23284] New: dmesg should identify the name of the stap script
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=23284
Bug ID: 23284
Summary: dmesg should identify the name of the stap script
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: serhei.public at gmail dot com
Target Milestone: ---
Many systemtap issues can be diagnosed by viewing dmesg output during a
testsuite run. Dmesg prints the module name when a stap module is loaded.
However, neither systemtap.sum nor systemtap.log record the stap module name
for every stap run, so it's not easy to tell which testcase caused a particular
warning.
This can be fixed by having the runtime print the original name of the script
file to dmesg.
The eBPF backend should also do this.
--
You are receiving this mail because:
You are the assignee for the bug.