From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-10247-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 8016 invoked by alias); 20 Oct 2008 20:10:13 -0000
Received: (qmail 5924 invoked by uid 48); 20 Oct 2008 20:08:58 -0000
Date: Mon, 20 Oct 2008 20:10:00 -0000
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20081020200858.6969.dsmith@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug tapsets/6969] New: syscall tapset broken on s390x
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2008-q4/txt/msg00155.txt.bz2

Syscall tracing seems to be broken on s390x arch. They are
failing in pass 2, with following errors:

 # stap buildok/syscall.stp -v
 Pass 1: parsed user script and 44 library script(s) in 420usr/10sys/434real ms.
 semantic error: unresolved arity-1 function: identifier 'pointer_arg' at
 /usr/share/systemtap/tapset/syscalls2.stp:3027:19
 semantic error: unresolved arity-1 function: identifier 'pointer_arg' at
 :3029:14
 semantic error: unresolved arity-1 function: identifier 'pointer_arg' at
 :3011:19
 semantic error: unresolved arity-1 function: identifier 'pointer_arg' at
 :3013:14
 Pass 2: analyzed script: 714 probe(s), 1866 function(s), 13 embed(s), 1
 global(s) in 6660usr/360sys/7064real ms.
 Pass 2: analysis failed.  Try again with more '-v' (verbose) options.

Function 'pointer_arg' (and related functions 'int_arg', 'uint_arg', etc.) comes
from tapset/ARCH/registers.stp for i386, ppc64, and x86_64.  Since registers.stp
doesn't exist for s390x, there is no definition for the *_arg functions.

If the 'pointer_arg' type functions are only designed to be used by the
nd_syscall tapset, then their use needs to be removed from syscalls2.stp.

-- 
           Summary: syscall tapset broken on s390x
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: dsmith at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=6969

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.