public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Matthew Ward <matthew.ward@fubra.com>
To: systemtap@sources.redhat.com
Cc: systemtap@sources.redhat.com
Subject: Re: usertap kernel read faults - can I ignore them somehow?
Date: Tue, 29 Nov 2011 15:02:00 -0000	[thread overview]
Message-ID: <4ED4F383.5030901@fubra.com> (raw)
Message-ID: <20111129150200.EJc3VmAGWpAeEEA_hsEOuP-e9Q6OFCKeMeabxYbOIrM@z> (raw)
In-Reply-To: <y0m8vmzvvsn.fsf@fche.csb>

On 29/11/2011 14:38, Frank Ch. Eigler wrote:
>
> 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<http://sourceware.org/PR13306>.
>
> - FChE
>

Thanks, that's exactly what I was looking for. When using the 
--skip-badvars option, if I'm running the tapset as a service using 
stapio, do I pass this to /usr/bin/stap when I build the original module 
(.ko) and this will apply whenever the module version is used by stapio 
etc. from then on?

Matt.

  reply	other threads:[~2011-11-29 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 14:30 Matthew Ward
2011-11-29 14:38 ` Frank Ch. Eigler
2011-11-29 15:00   ` Matthew Ward [this message]
2011-11-29 15:02     ` Matthew Ward
2011-11-29 17:02     ` Frank Ch. Eigler

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=4ED4F383.5030901@fubra.com \
    --to=matthew.ward@fubra.com \
    --cc=systemtap@sources.redhat.com \
    /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).