This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Trying Stapdyn Out
- From: Josh Stone <jistone at redhat dot com>
- To: sami wagiaalla <swagiaal at redhat dot com>
- Cc: systemtap at sourceware dot org
- Date: Mon, 20 Aug 2012 11:32:44 -0700
- Subject: Re: Trying Stapdyn Out
- References: <50327FFF.5050002@redhat.com>
On 08/20/2012 11:20 AM, sami wagiaalla wrote:
> Hi Josh,
Hi Sami, thanks for trying it.
> I was playing around with stapdyn following the instructions in your
> email [1]. I ran this:
>
> stap -e 'probe process.function("main") { println(pn()) }'
> --runtime=dyninst -c '/usr/bin/ls'
>
> and got the following error:
>
> Failed to create process /usr/bin/ls
> --SERIOUS-- #68: Failed to create process for /usr/bin/ls: Process
> exited during startup
> --FATAL-- #68: Dyninst was unable to create the specified process
> --FATAL-- #68: create process failed bootstrap
> WARNING: /usr/bin/stapdyn exited with status: 139
> Pass 5: run failed. Try again with another '--vp 00001' option.
I think I've seen something like this, and that exit 139 was a SIGFPE
somewhere in the dyninst library. But for me, the problem went away as
soon as I did "debuginfo-install dyninst". Of course that shouldn't be
required, and it certainly shouldn't crash with or without debuginfo,
but I haven't had a chance to dig into this issue yet.
I'll try to look again, and perhaps it's time for an updated snapshot of
both dyninst and systemtap. We're dealing with prereleases on both
fronts, so the water may be choppy. :)
Josh