From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8536 invoked by alias); 25 Jul 2011 19:36:20 -0000 Received: (qmail 8368 invoked by uid 22791); 25 Jul 2011 19:36:20 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_RW,TW_WX X-Spam-Check-By: sourceware.org Received: from mail-gx0-f169.google.com (HELO mail-gx0-f169.google.com) (209.85.161.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 25 Jul 2011 19:36:05 +0000 Received: by gxk23 with SMTP id 23so2796506gxk.0 for ; Mon, 25 Jul 2011 12:36:05 -0700 (PDT) Received: by 10.142.250.38 with SMTP id x38mr3068797wfh.30.1311622564684; Mon, 25 Jul 2011 12:36:04 -0700 (PDT) Received: from zdpc.mtv.corp.google.com ([2620:0:1000:1b02:baac:6fff:fe98:ceb5]) by mx.google.com with ESMTPS id m7sm4851418pbk.6.2011.07.25.12.36.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Jul 2011 12:36:03 -0700 (PDT) Message-ID: <4E2DC5A2.20403@gmail.com> Date: Mon, 25 Jul 2011 19:36:00 -0000 From: Da Zheng User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: William Cohen CC: "Turgis, Frederic" , "systemtap@sourceware.org" Subject: Re: error to run systemtap in an ARM platform References: <4E1F90A8.2080000@gmail.com> <1310722941.4510.5.camel@springer.wildebeest.org> <4E209C3F.6060806@gmail.com> <4E20A6EF.9010003@redhat.com> <4E20B11A.5020402@gmail.com> <13872098A06B02418CF379A158C0F1460162204601@dnce02.ent.ti.com> <4E243F49.9020706@redhat.com> <4E24831E.1000005@gmail.com> <4E249307.5050003@redhat.com> <4E249A82.8010404@gmail.com> <4E2D8FC2.2060901@redhat.com> In-Reply-To: <4E2D8FC2.2060901@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q3/txt/msg00098.txt.bz2 On 07/25/11 08:46, 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 > > > To try to replicate the problem on an arm machine running fedora 13 I ran the current build of systemtap from the git reposository and tried the iostats.stp example which should be accessing the $return: > > ./install/bin/stap -v systemtap/testsuite/systemtap.examples/io/iostats.stp > > This worked without problem on the locally built 2.6.31.14.24-efikamx linux kernel. This is a locally built kernel and systemtap is building things natively rather than attempting a cross compile. This is using: > > gcc-4.4.5-2.fc13.armv5tel > elfutils-0.146-1.fc13.armv5tel I use elfutils-0.131. Maybe the version of elfutils is too low. Let me see if I can build a newer version for my platform. > The following gives some suggestions on reporting bugs: > > http://sourceware.org/systemtap/wiki/HowToReportBugs > > These are "kernel("function_name").return"? What does list out as available at that probe point? > > stap -L 'kernel("function_name").return' $ stap -a arm -r /build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/build/tegra2_seaboard -L 'kernel.function("sys_read").return' kernel.function("sys_read@/build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/fs/read_write.c:402").return $return:long int $fd:unsigned int $buf:char* $count:size_t $file:struct file* $ret:ssize_t Thanks, Da