Re: Met Problem on Enable SystemTap on Android

["Yao,Yanjun" <jiaoyang28 at gmail dot com>]

Thanks Mark. I can get the syscall_by_pid.ko successfully.

However, when I run it in the "adb shell", I still got the syntax
error as following:
     # ./staprun syscalls_by_pid.ko
     ./staprun: 1: Syntax error: "(" unexpected

I know the reason is that my staprun is in x86 format. However, I do
follow the instructions on:
http://omappedia.org/wiki/Systemtap#Systemtap%201.5%20code%20update%20for%20OMAP%20ARM%20platforms

I run the following configuration before make install:
ac_cv_file__usr_include_avahi_common=no
ac_cv_file__usr_include_avahi_client=no
ac_cv_file__usr_include_nspr=no ac_cv_file__usr_include_nspr4=no
ac_cv_file__usr_include_nss=no ac_cv_file__usr_include_nss3=no
ac_cv_func_malloc_0_nonnull=yes ./configure
--exec-prefix=/data/systemtap-1.5-macharm
--prefix=/data/systemtap-1.5-macharm --host=arm-none-linux-gnueabi
CXXFLAGS=-static CFLAGS=-static --disable-translator --disable-docs
--disable-refdocs --disable-grapher --without-rpm
--with-elfutils=/home/lwan1/elfutils-0.143

However, the installed file is still in the format as following:
lwan1@ubuntu:/data$ file systemtap-1.5-macharm/bin/staprun
systemtap-1.5-macharm/bin/staprun: ELF 64-bit LSB executable, x86-64,
version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.15, from
'p)', not stripped

Any hints about why this is happening would be warmly welcomed.

Thank you very much.

Yours
Sincerely


2011/9/8 Mark Wielaard <mark@klomp.org>:
> On Wed, Sep 07, 2011 at 05:45:57PM -0400, Yao,Yanjun wrote:
>> Hi,
>>
>> I recompile the kernel with cross-compiler "arm-none-linux-gnueabi-"
>> and "make ARCH=arm"
>>
>> Now, I can get "helloworld.ko" from "helloworld.stp", however, when I
>> try to cross-compile "syscall_by_pid.stp", I got the following error
>> message:
>> ./stap -c -gv -a arm -D OMAP_L25 -B
>> CROSS_COMPILE=~/Downloads/arm-2010q1/bin/arm-none-linux-gnueabi- -r
>> /home/lwan1/WORKING_DIRECTORY/kernel_1 -I
>> /data/systemtap-1.5-macharm/share/systemtap/tapset/ -R
>> /data/systemtap-1.5-macharm/share/systemtap/runtime/ -m
>> syscalls_by_pid ~/Downloads/syscalls_by_pid.stp -c "sleep 0.2"
>> WARNING: kernel release/architecture mismatch with host forces last-pass 4.
>> semantic error: unresolved arity-4 function: identifier
>> '_arch_ptrace_argstr' at
>> /data/systemtap-1.5-ubuntu/share/systemtap/tapset/aux_syscalls.stp:2234:9
>> ??????? source: ??? retval=_arch_ptrace_argstr(request, pid, addr, data)
>> ??????????????? ??? ?????? ^
>> Pass 2: analysis failed.? Try again with another '--vp 01' option.
>>
>> I thought it was the problem of the tapset, so I reinstalled the
>> systemtap, but the problem is still there.
>>
>> Any hint would be welcome.
>
> This was fixed in current systemtap git sources by:
>
> commit 0c3087cc827a9e79abcf573e1a7ebfbc0be60c0e
> Author: William Cohen <wcohen@redhat.com>
> Date: ? Tue Jul 19 17:38:52 2011 -0400
>
> ? ?Add tapset/arm/aux_syscalls.stp
>
> ? ?The ARM processor needs to have _arch_ptrace_argstr() function defined
> ? ?so the kernel-debuginfo smoke test used for the "make installcheck" works.
>
> Cheers,
>
> Mark
>