This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: systemtap ARM port status
- From: Eugene Teo <eteo at redhat dot com>
- To: Quentin Barnes <qbarnes at urbana dot css dot mot dot com>
- Cc: Anderson Lizardo <anderson dot lizardo at gmail dot com>, systemtap at sources dot redhat dot com
- Date: Thu, 05 Jul 2007 16:18:06 +0800
- Subject: Re: systemtap ARM port status
- Organization: Red Hat, Inc
- References: <5b5833aa0706011152s7b33f9a8i3d6b8c6f0099694d@mail.gmail.com> <20070601193314.GE5831@urbana.css.mot.com>
Quentin Barnes wrote:
[...]
>> 1) On host: stap -p 4 -k script.stap
>> 2) Copy generated .ko to target
>> 3) On target: insmod stap-module.ko
>
> Well, for now I'm running completely native. Yes, that's very, very
> painful to run gcc and g++ on such a board with an NFS mounted file
> system and NFS mounted swap file over loopback. It can take four
> hours of wall time to compile and link the "stap" binary and the
> better part of a day to run the full testsuite.
Yes, it's very painful. I didn't run it completely native though. I ran
it in scratchbox, but it keeps on complaining that it is unable to find
the kernel debuginfo, even though it's there. I noticed that strace on
arm eabi seems to be buggy, and that didn't help. A simple hello world
stp script worked though. That is, step 1 and 2 (above), and step 3 using
staprun instead of insmod.
> I've had so many problems to solve getting Systemtap to support
> ARM, I didn't want to have to also deal with problems introduced
> from trying to get it to also support cross-builds simultaneously.
> I decided to work on one problem at a time.
Did you install it to /usr/local? I am wondering if you can tar it up,
and pass me a copy, so that I don't have to download compilers, etc onto
the device to install systemtap natively..
Eugene