This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/4913] probe syscall.* fails on i386 systems with systemtap-20070804
- From: "wenji dot huang at oracle dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 10 Aug 2007 08:18:36 -0000
- Subject: [Bug tapsets/4913] probe syscall.* fails on i386 systems with systemtap-20070804
- References: <20070810081102.4913.srinivasa@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From wenji dot huang at oracle dot com 2007-08-10 08:18 -------
Subject: Re: New: probe syscall.* fails on i386 systems
with systemtap-20070804
srinivasa,
"compat_do_execve" and "compat_sys_semtimedop" are functions for
providing for providing 32 bit
compatibility code in 64 bit systems.
So if your box is 32 bit, then report error.
It has been solved in latest source code (after 0804 snapshot).
Regards,
Wenji
srinivasa at in dot ibm dot com wrote:
>When I use probe syscall.* with the latest systemtap-20070804-snapshot,I got
>below error
>============================================
>[root@veda obj]# ./stap -e 'probe syscall.* {}'
>semantic error: no match for probe point while resolving probe point
>kernel.function("compat_do_execve")
>semantic error: no match for probe point while resolving probe point
>kernel.function("compat_sys_semtimedop")
>Pass 2: analysis failed. Try again with more '-v' (verbose) options.
>===============================================
>
>Looks like "compat_do_execve" and "compat_sys_semtimedop" syscall probes are
>moved to generic systemcall.stp tapsets(Instead of architecture specific
>systemcall tapset), Hence the error.
>
>
>
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4913
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.