| Summary: | nd_syscalls.stp tapset broken on ia64 | ||
|---|---|---|---|
| Product: | systemtap | Reporter: | David Smith <dsmith> |
| Component: | tapsets | Assignee: | Unassigned <systemtap> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | ia64 | Target: | |
| Build: | Last reconfirmed: | ||
Fixed in commit 60b8998. This commit adds support for kernel context argument access. |
On the ia64 platform, the nd_syscalls.stp tapset is broken. If you attempt to use it, you will get the following: # stap -p4 -v -e 'probe nd_syscall.accept { print(sockfd) }' Pass 1: parsed user script and 44 library script(s) in 310usr/7sys/317real ms. semantic error: unresolved arity-0 function: identifier 'asmlinkage' at /usr/share/systemtap/tapset/nd_syscalls.stp:46:2 semantic error: unresolved arity-1 function: identifier 'int_arg' at :47:11 semantic error: unresolved arity-1 function: identifier 'pointer_arg' at :48:15 semantic error: unresolved arity-1 function: identifier 'pointer_arg' at :49:18 Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 334usr/243sys/580real ms. Pass 2: analysis failed. Try again with more '-v' (verbose) options. This bug is related to bug #6969. The problem is there is no tapset/ia64/registers.stp file that would define the 'int_arg', 'pointer_arg', etc. functions.