From: fche@redhat.com (Frank Ch. Eigler)
To: Zhiwei Ying <zhiwei.ying@gmail.com>
Cc: systemtap <systemtap@sources.redhat.com>
Subject: Re: different result on cross-compile on fc12 and fc13
Date: Mon, 21 Mar 2011 14:31:00 -0000 [thread overview]
Message-ID: <y0md3lksfzf.fsf@fche.csb> (raw)
In-Reply-To: <AANLkTin4FkGnRf=7q0fw30K6fWR1N+hTxFT+zdpbA0DN@mail.gmail.com> (Zhiwei Ying's message of "Mon, 21 Mar 2011 10:28:02 +0800")
Zhiwei Ying <zhiwei.ying@gmail.com> writes:
> [...] If I compiled the trace.ko on fc13, then everything is
> fine. The trace log is generated correctly. But if I compiled the
> trace.ko on fc12, whatever I use the stap on fc12 or compile a
> systemtap 1.4 myself, I cannot see correct trace log on the board
> after running. [...]
One possibility is a mismatch between the version of stap on the host,
and the version of staprun installed on the board. There was a
module<->staprun interface change in commit #3abb860f (in stap 1.4)
that was unfortunately not done in a cross-compatible manner. You'd
see target kernel error (dmesg) messages of the form
STP_RELOCATE message size mismatch (%lu vs %lu)
If you upgrade your staprun on the target, and your development stap,
it should work again. We could change the next version of stap to
have its modules tolerate much older stapruns, if that's important.
- FChE
next prev parent reply other threads:[~2011-03-21 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 2:28 Zhiwei Ying
2011-03-21 9:55 ` Adrien Kunysz
2011-03-23 1:25 ` Zhiwei Ying
2011-03-23 1:53 ` Josh Stone
2011-03-23 2:25 ` Zhiwei Ying
2011-03-21 14:31 ` Frank Ch. Eigler [this message]
2011-03-22 0:22 ` Zhiwei Ying
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=y0md3lksfzf.fsf@fche.csb \
--to=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=zhiwei.ying@gmail.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).