This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/4281] two problems with "stap -m"
- From: "hunt at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 26 Mar 2007 18:42:10 -0000
- Subject: [Bug translator/4281] two problems with "stap -m"
- References: <20070326172231.4281.hunt@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From hunt at redhat dot com 2007-03-26 19:42 -------
(In reply to comment #5)
>
> Let's say you run "stap -m foo script1.stp" and we somehow cache the result.
> Then you run "stap -m foo script2.stp" - obviously you don't want the cached
> result, but we'd have no way of knowing that.
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)
--
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.