This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: error to run systemtap in an ARM platform
On 07/25/2011 03:55 PM, Da Zheng wrote:
> On 07/25/11 10:16, William Cohen wrote:
>> On 07/23/2011 06:55 PM, Zheng Da wrote:
>>> Hello,
>>>
>>> I'm still trying to fix the problem.
>>> semantic error: failed to retrieve return value location for vfs_write
>>> (/build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/fs/read_write.c):
>>> identifier '$return' at read-write.stp:7:6
>>> source: if ($return> 0) {
>>> ^
>>> I'm pretty sure CONFIG_DEBUG_INFO is enabled, and in
>>> /build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/build/tegra2_seaboard,
>>> a binary file vmlinux is 57MB. It should contain the debug information.
>>>
>>> (cr) zhengda@zdpc
>>> /build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-k
>>> ernel-9999/build/tegra2_seaboard $ ls -l vmlinux
>>> -rwxr-xr-x 1 zhengda portage 59419805 Jul 22 20:55 vmlinux
>>>
>>> How does systemtap use the debug information? When it compiles the
>>> script, does it need to read the debug information from the kernel
>>> image? or it needs to read the .obj files of the kernel?
>>> Any ideas how to debug the problem?
>>>
>>> Thanks,
>>> Da
>> I wonder if this might be Bug 440059 - Missing return value locations support for ARM in elfutils backend
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=440059
>>
>> How old is the version of elfutils you are using?
> Problem is solved. I used a latest version of elfutils, and systemtap can compile the script now.
>
> Thanks,
> Da
Hi Da,
Glad to hear that it is working with the newer elfutils. Which particular distribution of linux for arm are you using?
Are you planning on probing modules with systemtap? We have noticed that probing modules does not currently work on arm. There is a bug entry for it: http://sourceware.org/bugzilla/show_bug.cgi?id=13022
-Will