From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15679 invoked by alias); 16 Nov 2009 20:47:28 -0000 Received: (qmail 15622 invoked by uid 48); 16 Nov 2009 20:47:14 -0000 Date: Mon, 16 Nov 2009 20:47:00 -0000 Message-ID: <20091116204714.15621.qmail@sourceware.org> From: "dsmith at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070214005619.4037.fche@redhat.com> References: <20070214005619.4037.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/4037] make staprun 32/64-bit interoperable X-Bugzilla-Reason: AssignedTo 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: 2009-q4/txt/msg00537.txt.bz2 ------- Additional Comments From dsmith at redhat dot com 2009-11-16 20:47 ------- I've tested this issue for x86/x86_64, by testing 32-bit x86 binaries on an 64-bit x86_64 system. To ensure I was testing 32-bit executables, I built x86 rpms on the x86 system, then installed them on the x86_64 system. The testsuite results looked very similar to 64-bit testsuite results. Looking at the message definitions in runtime/transport/transport_msgs.h, it appears that they all are in the form int32_t/int64_t which looks correct. There are no plain 'int' or 'long' types there. Using '-DDEBUG_SYMBOLS' to see what sort of addresses the 32-bit staprun is sending the kernel shows this: # stap -DDEBUG_SYMBOLS -e 'probe kernel.function("sys_open") { printf("open\n") }' (02:29:45 PM) dsmith: _stp_module_relocate:79: kernel, _stext, 30690 (02:29:45 PM) dsmith: _stp_module_relocate:107: address=ffffffff80031690 That address is a 64-bit address, which is correct. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4037 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.