[Bug translator/4281] two problems with "stap -m"

[dsmith at redhat dot com]

------- Additional Comments From dsmith at redhat dot com  2007-03-26 19:52 -------
(In reply to comment #7)

> This is beyond the scope of this BZ. I am aware of the basics how stap caching
> works. But I don't think that rules out using the cache with -m.
> > stap script1.stp
> ( puts compiled script in long cached stap* name)
> > stap -m foo script1.stp
> (copies and renames the cached stap* module and loads that)

True.  But, that disallows the user from using the cached file directly.

# stap -p4 begin.stp 
/home/dsmith/.systemtap/cache/fc/stap_fc1322dcb34cdb7c96679435f22df754_264.ko
# staprun
/home/dsmith/.systemtap/cache/fc/stap_fc1322dcb34cdb7c96679435f22df754_264.ko
... script runs ...

The above will work correctly.  However, if we do the same thing with '-m', it
would fail, since the cached file couldn't be used directly - it has to be
renamed first.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4281

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.