From: Adrien Kunysz <adrien@kunysz.be>
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 09:55:00 -0000 [thread overview]
Message-ID: <20110321095511.GA16725@baltika> (raw)
In-Reply-To: <AANLkTin4FkGnRf=7q0fw30K6fWR1N+hTxFT+zdpbA0DN@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Mon, Mar 21, 2011 at 10:28:02AM +0800, Zhiwei Ying wrote:
> I have a develop board, which runs linux 2.6.35. The board is
> connected to a fedora 12. I cross-compile the systemtap script to
> generate trace.ko, and copy the trace.ko to run the instrumented code
> on the board.
>
> 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. The trace.ko
> cannot generate any log from application, but only able to trace
> probe.end.
>
> I didn't see any compile error msg on fc12 system.
>
> Any idea to solve this problem. I cannot drop fc12 now and don't want
> to use another fc13 to compile the script.
I would rebuild both the working and non-working versions of the module
with -vvvvv and try to find any difference in there. Failing that, I
would look at differences in the modules themselves (maybe with objdump
and diff) then try to figure out where it comes from.
A more detailed description of what (doesn't) work(s) would also help.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-03-21 9:55 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 [this message]
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
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=20110321095511.GA16725@baltika \
--to=adrien@kunysz.be \
--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).