This is the mail archive of the
mailing list for the systemtap project.
testsuite/buildok/syscall.stp failed due to unresolved target-symbol
- From: Li Guanglei <guanglei at cn dot ibm dot com>
- To: "systemtap at sourceware dot org" <systemtap at sourceware dot org>
- Date: Mon, 24 Jul 2006 14:39:02 +0800
- Subject: testsuite/buildok/syscall.stp failed due to unresolved target-symbol
- Organization: IBM CSTL
testsuite/buildok/syscall.stp failed on my ppc64 because of
unresolved target-symbol, which has already been addressed in BZ 2438.
So we must check the current syscall tapsets to make the changes
/* FIXME: RHEL4 U3 ppc64 can't resolve $fd */
%( arch != "ppc64" %?
fd = $fd
argstr = sprintf("%d, %p, %d", $fd, $vec, $vlen)
argstr = sprintf("unknown fd, %p, %d", $vec, $vlen)
One trouble with this is that if $fd can't be resolved, the tapsets
just set fd=0. The user will think fd=0 is the actual value and won't
realize the error. So how about setting fd and other unresolved target
symbol to an obvious error value, for example, fd = -1 ?