This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/4037] make staprun 32/64-bit interoperable
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 16 Nov 2009 20:47:14 -0000
- Subject: [Bug runtime/4037] make staprun 32/64-bit interoperable
- References: <20070214005619.4037.fche@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- 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.