This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: Expected errors from make check?
- From: "Spirakis, Charles" <charles dot spirakis at intel dot com>
- To: <penghb2002 at yahoo dot com dot cn>
- Cc: <systemtap at sources dot redhat dot com>
- Date: Mon, 29 Aug 2005 18:59:53 -0700
- Subject: RE: Expected errors from make check?
Using a similar modification (I used pushd/popd instead of cd), I get the same failures. Interestingly, if I add the -v into the failing scripts, they then are listed as passing...
-- charles
The output of the five.stp without -v (from the command line - same as the make check error):
[cspiraki@cspiraki-lnote src]$ testsuite/buildok/five.stp
Pass 4: compilation failed. Try again with '-v' (verbose) option.
The output of the five.stp with the -v option (from the command line - make check says success):
[cspiraki@cspiraki-lnote src]$ testsuite/buildok/five.stp
stap: invalid option --
SystemTap translator/driver (version 0.3.1 built 2005-08-29)
Copyright (C) 2005 Red Hat, Inc.
This is free software; see the source for copying conditions.
Usage: stap [options] FILE Run script in file.
or: stap [options] - Run script on stdin.
or: stap [options] -e SCRIPT Run given script.
Options:
-- no more options after this
-v verbose [set]
-h show help
-V show version
-k keep temporary directory
-g guru mode
-p NUM stop after pass NUM 1-5
(parse, elaborate, translate, compile, run)
-I DIR look in DIR for additional .stp script files, in addition to
/usr/local/share/systemtap/tapset
-R DIR look in DIR for runtime, instead of
/usr/local/share/systemtap/runtime
-m MODULE set probe module name, instead of
stap_500_1125366877
-o FILE send output to file instead of stdout
> -----Original Message-----
> From: systemtap-owner@sources.redhat.com
> [mailto:systemtap-owner@sources.redhat.com] On Behalf Of Peng Hongbo
> Sent: Monday, August 29, 2005 6:27 PM
> To: Spirakis, Charles
> Cc: systemtap@sources.redhat.com
> Subject: Re: Expected errors from make check?
>
> ======= 2005-08-29 17:06:00 from Spirakis, Charles=======
>
> >All --
> >
> >Seems like there may be a path issue or something with the makefile
> >check/test scripts (see below). System is i686 running FC4 using the
> >elfutils 114 via SRPMS.
> >
>
> After modifying runtest.sh, I found 4 FAILs.
>
> FAIL: ./testsuite/buildok/five.stp
> FAIL: ./testsuite/buildok/four.stp
> FAIL: ./testsuite/buildok/seven.stp
> FAIL: ./testsuite/buildok/six.stp
>
> For four.stp, the detail err log is:
> # ./runtest.sh testsuite/buildok/four.stp -v # cat
> testsuite/buildok-four.stp.err Created temporary directory
> "/tmp/stapfz7WkA"
> Searched '/tmp/systemtap/src/tapset/2.6.11-1.1369_FC4/*.stp',
> match count 0 Searched
> '/tmp/systemtap/src/tapset/2.6.11/*.stp', match count 0
> Searched '/tmp/systemtap/src/tapset/2.6/*.stp', match count 0
> Searched '/tmp/systemtap/src/tapset/*.stp', match count 3
> Pass 1: parsed user script and 3 library script(s).
> parsed '*' -> func '*'
> pattern 'ext3' matches module 'ext3'
> focused on module 'ext3' = [cca56000-cca765c9, bias 0]
> WARNING: dwfl_module_getdwarf() : relocation refers to
> undefined symbol
> WARNING: no dwarf info found for module ext3 semantic error:
> no match for probe point
> while: resolving probe point
> module("ext3").function("*") Pass 2: analyzed user script. 0
> probe(s), 0 function(s), 0 global(s).
> Pass 2: analysis failed. Try again with '-v' (verbose) option.
> Running /bin/rm -rf /tmp/stapfz7WkA
> #
>
>
>
> --- src/runtest.sh 2005-08-21 20:11:41.000000000 +0800
> +++ src.new/runtest.sh 2005-08-30 10:07:47.000000000 +0800
> @@ -6,8 +6,8 @@ if [ ! -d testsuite ]; then
> mkdir -p testsuite
> fi
>
> -SRCDIR=`dirname $0`
> -export SRCDIR
> +cd `dirname $0`
> +export SRCDIR=${PWD}
>
> SYSTEMTAP_TAPSET=$SRCDIR/tapset
> export SYSTEMTAP_TAPSET
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> 雅虎免费G邮箱-中国第一绝无垃圾邮件骚扰超大邮箱
> http://cn.mail.yahoo.com/?id=77071
>
>