From: Eric Wong <normalperson@yhbt.net>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Systemtap List <systemtap@sourceware.org>
Subject: Re: copy faults from user_string* functions
Date: Fri, 26 Jul 2013 17:56:00 -0000 [thread overview]
Message-ID: <20130726175602.GA5773@dcvr.yhbt.net> (raw)
In-Reply-To: <y0miozxmeqe.fsf@fche.csb>
"Frank Ch. Eigler" <fche@redhat.com> wrote:
> normalperson wrote:
> > Hi all, just to clarify, not all of these faults are user errors, right?
> > I get these sometimes with some strings (constants, I think):
> > ERROR: user string copy fault -14 at 000000000042f16c near identifier 'user_string_n' at $prefix/share/systemtap/tapset/uconversions.stp:120:10
> > [...]
>
> It can simply mean having some not-yet-paged-in data, which in the
> spirit of non-interference, stap will not trigger a page fault for.
> Please try error-catching constructs such as try{}catch{}, or
> --skip-badvars to tolerate them.
Hi Frank, thanks for the response. --skip-badvars seems to work for me.
Is there any optional way to get stap to trigger page faults to get
that data?
When tracing, losing a little performance is OK, especially with
cmogstored (which is entirely network/disk bound).
> > This is for cmogstored, if anybody is interested in reproducing this,
> > I've pushed my work-in-progress to the "st-wip-broken" branch of
> > git://bogomips.org/cmogstored.git The HACKING doc in the top-level
> > should document all the build-dependencies if you want to try to
> > reproduce it.
>
> Neat.
>
> - FChE
--
Eric Wong
next prev parent reply other threads:[~2013-07-26 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 6:36 Eric Wong
2013-07-26 17:08 ` Frank Ch. Eigler
2013-07-26 17:56 ` Eric Wong [this message]
2013-07-26 19:42 ` Eric Wong
2013-07-26 19:50 ` Eric Wong
2013-07-27 0:22 ` 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=20130726175602.GA5773@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=fche@redhat.com \
--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).