public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Nan Xiao <xiaonan830818@gmail.com>
To: systemtap@sourceware.org
Subject: Is there any better method to pass "-d OBJECT" options in command line?
Date: Tue, 10 Nov 2015 05:48:00 -0000	[thread overview]
Message-ID: <CA+MhoaM6TZ78MwftPq=KzEjxJDLoSspgr=vdhZe=7J9OTK9Sbw@mail.gmail.com> (raw)

Hi all,

I want  to track which functions calling fork, so I modify forktracker.stp
(https://sourceware.org/systemtap/examples/process/forktracker.stp):

probe kprocess.create {
  printf("%-25s: %s (%d:%d) created %d:%d\n",
         ctime(gettimeofday_s()), execname(), pid(), tid(), new_pid, new_tid)

  print_ubacktrace();
}

probe kprocess.exec {
  printf("%-25s: %s (%d) is exec'ing %s\n",
         ctime(gettimeofday_s()), execname(), pid(), filename)
  print_ubacktrace()
}

But after executing the script, I find it sometimes prompts warnings:

WARNING: Missing unwind data for module, rerun with 'stap -d
/usr/lib64/libpython2.7.so.1.0'
......
WARNING: Missing unwind data for module, rerun with 'stap -d
.../lib64/libvirt/connection-driver/libvirt_driver_interface.so'
WARNING: Missing unwind data for module, rerun with 'stap -d /bin/bash'


I can use "stap -d /usr/lib64/libpython2.7.so.1.0 -d .. -d ...
forktracker.stp" to resolve
this issue. But if there are many lacking libraries, the "-d ..."
options will cause command line
too long.

So my question is whether there is a better method to specify these
lacked "*.so" files?

Thanks in advance!

Best Regards
Nan Xiao

             reply	other threads:[~2015-11-10  5:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10  5:48 Nan Xiao [this message]
2015-11-10 14:24 ` 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='CA+MhoaM6TZ78MwftPq=KzEjxJDLoSspgr=vdhZe=7J9OTK9Sbw@mail.gmail.com' \
    --to=xiaonan830818@gmail.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).