From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31082 invoked by alias); 29 Nov 2011 14:38:21 -0000 Received: (qmail 30968 invoked by uid 22791); 29 Nov 2011 14:38:21 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 29 Nov 2011 14:38:02 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pATEc1Zm026818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 29 Nov 2011 09:38:01 -0500 Received: from fche.csb (vpn-8-102.rdu.redhat.com [10.11.8.102]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pATEc1K1014139; Tue, 29 Nov 2011 09:38:01 -0500 Received: by fche.csb (Postfix, from userid 2569) id D60355814E; Tue, 29 Nov 2011 09:38:00 -0500 (EST) To: Matthew Ward Cc: systemtap@sources.redhat.com Subject: Re: usertap kernel read faults - can I ignore them somehow? References: From: fche@redhat.com (Frank Ch. Eigler) Date: Tue, 29 Nov 2011 14:38:00 -0000 In-Reply-To: (Matthew Ward's message of "Tue, 29 Nov 2011 14:20:12 +0000") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q4/txt/msg00235.txt.bz2 Hi, Matthew - > I'm having an issue with our usertap tapset > (https://github.com/fubralimited/usertap) [...] > ERROR: kernel read fault at 0x0000000100000264 (addr) near identifier > '@cast' at /usr/share/systemtap/tapset/ip.stp:45:11 You can do several things. First, you can run "stap --skip-badvars ...", which turns all erroneous $var accesses into 0. Second, you can (sometimes) wrap expressions with try { var = $var } catch { } to absorb the error. But see . - FChE