The bug is in your module's unconditional use of UTRACE_*STEP.
It's documented that it's invalid to use them unless arch_has_*_step()
has returned true. (The utrace_resume_action description refers you
to utrace_control(), where this is documented.)
It's a bug to use these at all when the corres
Hi,
In regards to the instruction tracing probe points that were added to SystemTap
last year, Frank had asked whether the block-trace functionality (.insn.block)
is working. I tested this on x86_64/Fedora 10 and, indeed, it does work.
However, when testing on a ppc64 system, it failed terribl
Srinivasa Ds wrote:
Hi
I was executing Alexey's testcase cited in
(http://marc.info/?l=linux-kernel&m=117128445312243&w=2) to test the utrace and
system crashed on pressing ctr+c.
This leads me to suspect a possible issue with the usage of RCU in utrace.
Please let me know your commen
Hi
I was executing Alexey's testcase cited in
(http://marc.info/?l=linux-kernel&m=117128445312243&w=2) to test the utrace and
system crashed on pressing ctr+c.
Environment: 2.6.23-rc7, ppc64.
6:mon> e
cpu 0x6: Vector: 300 (Data Access) at [c0002510b650]
pc: c038b0f8: ._spin
