public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Lukas Berk <lberk@redhat.com>
To: systemtap <systemtap@sourceware.org>
Cc: swood@fotofor.biz
Subject: Re: freezes stap
Date: Mon, 23 Jul 2018 14:22:00 -0000	[thread overview]
Message-ID: <87y3e26ngs.fsf@redhat.com> (raw)
In-Reply-To: <CAKFOr-bD1JP1e4qbC+vRroeUicn5q9gAqcCqiCejWRSpN8_r=A@mail.gmail.com>	(David Smith's message of "Thu, 19 Jul 2018 15:54:21 -0500")

Hi,

A somewhat tangential thought,

David Smith <dsmith@redhat.com> 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

  reply	other threads:[~2018-07-23 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 15:38 Anton Kiryushkin
2018-07-19 20:39 ` David Smith
2018-07-19 20:47   ` Anton Kiryushkin
2018-07-19 20:54     ` David Smith
2018-07-23 14:22       ` Lukas Berk [this message]
2018-07-23 20:01         ` David Smith
2018-07-23 20:48           ` Lukas Berk
2018-07-26 15:24             ` Anton Kiryushkin
2018-07-26 19:07               ` David Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3e26ngs.fsf@redhat.com \
    --to=lberk@redhat.com \
    --cc=swood@fotofor.biz \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).