public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Klein, Matt" <mklein@amazon.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Issues with probing multiple modules in script
Date: Wed, 28 Dec 2011 08:07:00 -0000	[thread overview]
Message-ID: <FCDCC4AE6C28B44B90993D9894683575B35B07D5@EX-SEA3-A.ant.amazon.com> (raw)

Hi,

I'm having some strange issues trying to probe multiple modules in the same script. For starters:

[~/AmazonData/Source/stap]$ stap -V
SystemTap translator/driver (version 1.3/0.152 non-git sources)

If I try to probe a single module, everything works as expected. However if I probe multiple modules, it seems like probes in the first module found works fine, but any probes on subsequent modules don't actually work. I also see the following error for all modules other than the first:

WARNING: missing unwind/symbol data for module ...

Here is how I am invoking stap:
stap -p4 -m test -r /home/mklein/AmazonData/Source/linux test.stp

I have looked through the -vvvvv output, and it looks to me like all of the module probe points are being identified correctly, but then I see the WARNING message and it doesn't look like the probes ever actually get invoked.

I know that that the other module probes are correct, because if I probe them in isolation, everything works as expected.

Is there anything obvious I am doing wrong (like probing multiple modules from the same script doesn't work)? If not, what data can I provide to help get to the bottom of this?

Thanks,
Matt

--
Matt Klein
Senior Software Engineer
Amazon Web Services
mklein@amazon.com / 206-266-3347

             reply	other threads:[~2011-12-27 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  8:07 Klein, Matt [this message]
2011-12-31  1:33 ` 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=FCDCC4AE6C28B44B90993D9894683575B35B07D5@EX-SEA3-A.ant.amazon.com \
    --to=mklein@amazon.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).