From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21443 invoked by alias); 22 Mar 2011 00:22:26 -0000 Received: (qmail 21431 invoked by uid 22791); 22 Mar 2011 00:22:23 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-gw0-f47.google.com (HELO mail-gw0-f47.google.com) (74.125.83.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Mar 2011 00:22:18 +0000 Received: by gwb11 with SMTP id 11so3610555gwb.20 for ; Mon, 21 Mar 2011 17:22:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.104.8 with SMTP id b8mr4406415ybc.358.1300753336313; Mon, 21 Mar 2011 17:22:16 -0700 (PDT) Received: by 10.147.83.3 with HTTP; Mon, 21 Mar 2011 17:22:16 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Mar 2011 00:22:00 -0000 Message-ID: Subject: Re: different result on cross-compile on fc12 and fc13 From: Zhiwei Ying To: "Frank Ch. Eigler" Cc: systemtap Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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-q1/txt/msg00506.txt.bz2 Actually I am using staprun 1.4 on the board, and compiled same version on the host. I am moving to Ubuntu to see if there is any lucky. On Mon, Mar 21, 2011 at 10:30 PM, Frank Ch. Eigler wrote: > Zhiwei Ying writes: > >> [...] =A0If 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. =A0There was a > module<->staprun interface change in commit #3abb860f (in stap 1.4) > that was unfortunately not done in a cross-compatible manner. =A0You'd > see target kernel error (dmesg) messages of the form > > =A0 =A0STP_RELOCATE message size mismatch (%lu vs %lu) > > If you upgrade your staprun on the target, and your development stap, > it should work again. =A0We could change the next version of stap to > have its modules tolerate much older stapruns, if that's important. > > - FChE >