public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Indraneel Mukherjee <indro.ml@gmail.com>
To: Eugeniy Meshcheryakov <eugen@debian.org>
Cc: systemtap@sources.redhat.com
Subject: Re: systemtap-1.0.0 runtime failure on ARM - simple stap script  	translation fails
Date: Mon, 14 Dec 2009 12:25:00 -0000	[thread overview]
Message-ID: <48e37220912140425h3ce1a3en3efb276d69d9ee9d@mail.gmail.com> (raw)
In-Reply-To: <20091214110045.GA6906@localhost.localdomain>

Hi Eugeniy,

On Mon, Dec 14, 2009 at 4:30 PM, Eugeniy Meshcheryakov <eugen@debian.org> wrote:
> Yes, I know about that problem. But I'm not sure whether proposed patch
> fixes anything. Were you able to _use_ modules made with that patch applied?

Yes, i was able to _use_ SystemTap on ARM after applying that patch +
your fix. I ran the following script and it worked absolutely fine:

global reads
probe kernel.function("do_writepages") {
        reads[execname()]++
        }
probe timer.s(3)
{
        foreach (count in reads)
                printf("%s : %d \n", count, reads[count])
}

OUTPUT of script:
pdflush : 4
pdflush : 4
pdflush : 8
pdflush : 8
pdflush : 12
pdflush : 12
pdflush : 12
...
...
> Or does it fixes only compilation? My guess is that module
> initialization will fail because build-id does not match.

No it does not fail.

Regards,
Indro

>
> 14 грудня 2009 о 16:11 +0530 Indraneel Mukherjee написав(-ла):
>> Thanks for the fix. Also, there was another patch that i had to apply
>> to get Systemtap working for ARM. I checked the latest git and the fix
>> is not available for ARM. The fix is here:
>> http://sources.redhat.com/ml/systemtap/2009-q4/msg00574.html
>> Without the above fix, the ARM(arm-linux is non-relocatable) stap FAILS.
>>
>> This is related to
>> http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg690166.html
>>
>> Shouldn't this fix be added to the Systemtap tree to get it right for ARM?
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAksmGt0ACgkQKaC6+zmozOLZtwCfasFxn9Q8LgZgLQ59sKIEyJT3
> dEMAoJC1rOkL/NN+mABa5p16hDqXMMV1
> =ud4E
> -----END PGP SIGNATURE-----
>
>

  reply	other threads:[~2009-12-14 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14  5:55 Indraneel Mukherjee
2009-12-14  7:09 ` Eugeniy Meshcheryakov
2009-12-14  7:12   ` Eugeniy Meshcheryakov
2009-12-14 10:41     ` Indraneel Mukherjee
2009-12-14 11:00       ` Eugeniy Meshcheryakov
2009-12-14 12:25         ` Indraneel Mukherjee [this message]
2009-12-14 15:26           ` Eugeniy Meshcheryakov
2009-12-15 13:50           ` Eugeniy Meshcheryakov
2009-12-17  6:09             ` naresh kamboju

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=48e37220912140425h3ce1a3en3efb276d69d9ee9d@mail.gmail.com \
    --to=indro.ml@gmail.com \
    --cc=eugen@debian.org \
    --cc=systemtap@sources.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).