This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: please help
Breno Leitao wrote:
> Peter,
>
> Peter Teoh wrote:
>> Alternatively, as Frank earlier said in another email:
>>
>> probe process("a.out").function("*") { log ($$parms) }
>
> On PPC, I am getting the following error when running this code:
>
> [root@otitis systemtap]# stap userspace.stp -v
> Pass 1: parsed user script and 45 library script(s) in 320usr/0sys/326real ms.
> semantic error: ELF machine ppc (code 20) mismatch with target ppc64 in '/root/systemtap/a.out'
> semantic error: no match while resolving probe point process("a.out").function("*")
> semantic error: no probes found
> Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 0usr/0sys/7real ms.
> Pass 2: analysis failed. Try again with more '-v' (verbose) options.
>
> Isn't the process tracing supported on the PPC platform ?
It appears that systemtap is complaining that you are trying to put
probes in a ppc (32-bit) executable while running a ppc64 (64-bit)
kernel. Unfortunately, that is the normal case on a ppc64 box (if I
remember correctly).
Can you try compiling the a.out as a ppc64 executable and see if that works?
If I'm reading tapsets.cxx correctly, the same problem will happen when
trying to probe an x86 program on a system with a x86_64 kernel.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)