Summary: | Probe definitions over kernel markers isn't recognised | ||
---|---|---|---|
Product: | systemtap | Reporter: | K.Prasad <prasad> |
Component: | runtime | Assignee: | Unassigned <systemtap> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
K.Prasad
2008-12-12 14:21:05 UTC
(In reply to comment #0) > The following logs will help understand the problem better. The following error message will help too: :-) > semantic error: probe point mismatch at position 1 (alternatives: > function(number) function(string) mark(string) statement(number) ************ > statement(string)): identifier 'kernel' at marker_example.stp:1:7 [...] IOW, use kernel.mark("..."), not kernel.marker("..."). (In reply to comment #1) > (In reply to comment #0) > IOW, use kernel.mark("..."), not kernel.marker("..."). BTW, I've regretted the choice of 'kernel.mark' instead of 'kernel.marker' myself, even though I probably chose it. The kernel function being named 'trace_mark' instead of 'trace_marker' threw me off I guess... |