This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Is there any better method to pass "-d OBJECT" options in command line?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Nan Xiao <xiaonan830818 at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Tue, 10 Nov 2015 09:24:30 -0500
- Subject: Re: Is there any better method to pass "-d OBJECT" options in command line?
- Authentication-results: sourceware.org; auth=none
- References: <CA+MhoaM6TZ78MwftPq=KzEjxJDLoSspgr=vdhZe=7J9OTK9Sbw at mail dot gmail dot com>
Nan Xiao <xiaonan830818@gmail.com> writes:
> [...]
> 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'
> [...]
> So my question is whether there is a better method to specify these
> lacked "*.so" files?
See the "--ldd" option, which includes all shared libraries
transitively referenced from all binaries named with "-d BIN".
So it may be enough to name a few of the higher-level binaries
& libraries explicitly, and let --ldd pull in their dependencies.
- FChE