From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100539 invoked by alias); 23 Jul 2018 14:22:48 -0000 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 Received: (qmail 100531 invoked by uid 89); 23 Jul 2018 14:22:47 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=spare, stap, H*Ad:D*biz, our X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 23 Jul 2018 14:22:46 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C4B5E40241D2; Mon, 23 Jul 2018 14:22:44 +0000 (UTC) Received: from toium (unused-10-15-17-37.yyz.redhat.com [10.15.17.37]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7A3217C3E; Mon, 23 Jul 2018 14:22:44 +0000 (UTC) From: Lukas Berk To: systemtap Cc: swood@fotofor.biz Subject: Re: freezes stap References: Date: Mon, 23 Jul 2018 14:22:00 -0000 In-Reply-To: (David Smith's message of "Thu, 19 Jul 2018 15:54:21 -0500") Message-ID: <87y3e26ngs.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-q3/txt/msg00034.txt.bz2 Hi, A somewhat tangential thought, David Smith writes: >>> 2) WARNING: probe kernel.function("vfs_read@../fs/read_write.c:418") >>> (address 0xffffffff95232f70) registration error (rc -84) >>> >>> That one is fairly fatal. Your probe couldn't be registered, and >>> returned -84. Since your probe couldn't be registered, the module >>> won't really do anything. >From a usability standpoint, could we possibly keep track of the number of targeted probe points vs successfully registered probe points? In the event none exist, perhaps it'd be worthwhile to exit on our own volition. It might spare users the extra time trying to debug the issue with a message elaborating on why (ie, no probe points actually registered, nothing for us to do). Cheers, Lukas