From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28387 invoked by alias); 21 Mar 2011 14:31:01 -0000 Received: (qmail 28373 invoked by uid 22791); 21 Mar 2011 14:31:00 -0000 X-SWARE-Spam-Status: No, hits=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Mar 2011 14:30:47 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p2LEUj3Q032033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 21 Mar 2011 10:30:45 -0400 Received: from fche.csb (vpn-8-169.rdu.redhat.com [10.11.8.169]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p2LEUjs6031996; Mon, 21 Mar 2011 10:30:45 -0400 Received: by fche.csb (Postfix, from userid 2569) id 8F1A75813A; Mon, 21 Mar 2011 10:30:44 -0400 (EDT) To: Zhiwei Ying Cc: systemtap Subject: Re: different result on cross-compile on fc12 and fc13 References: From: fche@redhat.com (Frank Ch. Eigler) Date: Mon, 21 Mar 2011 14:31:00 -0000 In-Reply-To: (Zhiwei Ying's message of "Mon, 21 Mar 2011 10:28:02 +0800") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00505.txt.bz2 Zhiwei Ying 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