This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug kprobes/13819] New: A Call Trace is generated when stap is run if the kernel option "Debug access to per_cpu maps" is enabled
- From: "kevincolbert33 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 08 Mar 2012 00:14:24 +0000
- Subject: [Bug kprobes/13819] New: A Call Trace is generated when stap is run if the kernel option "Debug access to per_cpu maps" is enabled
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13819
Bug #: 13819
Summary: A Call Trace is generated when stap is run if the
kernel option "Debug access to per_cpu maps" is
enabled
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: kprobes
AssignedTo: systemtap@sourceware.org
ReportedBy: kevincolbert33@gmail.com
Classification: Unclassified
Created attachment 6266
--> http://sourceware.org/bugzilla/attachment.cgi?id=6266
stap-report
SystemTap version 1.7 - If the kernel option "Debug access to per_cpu maps" is
enabled a Call Trace is generated when stap is run. The script parameters that
stap executes doesn't seem to make a difference, every script that I tried
would cause the Call Trace to be generated. A simple one liner like "stap -v
-e 'probe kernel.function("vfs_read") {printf("%s\n", $$parms); exit(); }'"
will generate the Call Trace. If the "Debug access to per_cpu maps" kernel
option is disabled the Call Trace will not be generated. Please see the
attached stap-report log file for all of the details.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.