From: Da Zheng <zhengda1936@gmail.com>
To: William Cohen <wcohen@redhat.com>
Cc: "Turgis, Frederic" <f-turgis@ti.com>,
"systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Re: error to run systemtap in an ARM platform
Date: Mon, 25 Jul 2011 19:56:00 -0000 [thread overview]
Message-ID: <4E2DCA44.4010007@gmail.com> (raw)
In-Reply-To: <4E2DA500.7090005@redhat.com>
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
next prev parent reply other threads:[~2011-07-25 19:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 0:58 Da Zheng
2011-07-15 9:43 ` Mark Wielaard
2011-07-15 20:00 ` Da Zheng
2011-07-15 20:15 ` Frank Ch. Eigler
[not found] ` <4E20A714.9020404@gmail.com>
2011-07-15 20:50 ` Frank Ch. Eigler
2011-07-15 20:46 ` William Cohen
2011-07-15 21:29 ` Da Zheng
2011-07-16 0:23 ` Turgis, Frederic
2011-07-18 14:13 ` William Cohen
2011-07-18 19:02 ` Da Zheng
2011-07-18 20:10 ` William Cohen
2011-07-18 20:18 ` William Cohen
2011-07-18 20:41 ` Da Zheng
2011-07-23 22:56 ` Zheng Da
2011-07-24 1:57 ` Frank Ch. Eigler
2011-07-24 16:10 ` Frank Ch. Eigler
2011-07-25 10:04 ` Mark Wielaard
2011-07-25 19:34 ` Da Zheng
2011-07-25 15:46 ` William Cohen
2011-07-25 19:36 ` Da Zheng
2011-07-25 20:46 ` Mark Wielaard
2011-07-25 17:17 ` William Cohen
2011-07-25 19:56 ` Da Zheng [this message]
2011-07-26 14:03 ` William Cohen
2011-07-26 17:47 ` Da Zheng
2011-07-19 11:38 ` Turgis, Frederic
2011-07-18 14:00 ` William Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E2DCA44.4010007@gmail.com \
--to=zhengda1936@gmail.com \
--cc=f-turgis@ti.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).