This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/4037] make staprun 32/64-bit interoperable


------- Additional Comments From hunt at redhat dot com  2007-02-14 02:10 -------
(In reply to comment #0)
> Please investigate why a 32-bit staprun fails to work against a 64-bit kernel. 

I intentionally disabled it because it was making a lot of code very messy. Also
I thought it provided an additional check that the systemtap you were attempting
to run was configured and compiled correctly.

The code that parses the kernel and module symbols and passes those back to the
kernel module for storage passes pointers and structures containing pointers. If
staprun has to dynamically detect mismatches and still work, that means more
complicated and potentially slower and buggier code. Still, it can be done and
isn't really a big deal, but what is the motivation?  I am confused about how
this situation occurred and why it is desireable to have 32-bit stapruns work on
64-bit kernels.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]