public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Tim Beaulen <tbscope@gmail.com>
Cc: systemtap@sources.redhat.com
Subject: Re: UProbes fails
Date: Fri, 03 Sep 2010 07:14:00 -0000	[thread overview]
Message-ID: <1283498048.10596.2.camel@springer.wildebeest.org> (raw)
In-Reply-To: <AANLkTikQkdJC-8raUGsFDTSYdyuyZZNDR67hvgj723a2@mail.gmail.com>

On Fri, 2010-09-03 at 08:55 +0200, Tim Beaulen wrote:
> If uprobes requires the source files to be available, then that might
> be the problem.
> By accident, the source files got removed after building.

No, stap only needs the dwarf debuginfo to know where to place the
probes. You might want to look in the kernel logs (dmesg) if there are
any hints there about why the placement of the uprobes didn't work.

Cheers,

Mark

  reply	other threads:[~2010-09-03  7:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  6:01 Tim Beaulen
2010-09-03  6:55 ` Tim Beaulen
2010-09-03  7:14   ` Mark Wielaard [this message]
     [not found]     ` <AANLkTimHwKuUUDxPjfmtMfaByj=cX8HqK-PaAheM8dih@mail.gmail.com>
2010-09-03 18:27       ` Tim Beaulen
2010-09-03 19:49         ` Jim Keniston

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=1283498048.10596.2.camel@springer.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=tbscope@gmail.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).