Bug 4295

Summary:	"stap -m" enhancement
Product:	systemtap	Reporter:	David Smith <dsmith>
Component:	translator	Assignee:	Unassigned <systemtap>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	hunt
Priority:	P2
Version:	unspecified
Target Milestone:	---
Host:		Target:
Build:		Last reconfirmed:
Attachments:	Store resulting module in current directory

Description David Smith 2007-03-29 17:24:15 UTC

This enhancement has been split off from bug #4281

When running "stap -m close close.stp", where's close.ko?  I shouldn't need to
also use -k.

Perhaps when using '-m NAME', the resulting module (if any) should be copied to
the current directory.

For more discussion, see original bug.

Comment 1 William Cohen 2007-07-26 18:17:42 UTC

Created attachment 1933 [details]
Store resulting module in current directory

This patch is an attempt to handle the common use case where someone wants to
generate an instrumentation module that will be used repeatedly with staprun.
The patch copies the resulting file into the current directory before removing
the temporary directory. The patch also limits the systemtap to pass pass 4
when the -m command is used. The instrumentaiton is not run at that momemt

Comment 2 David Smith 2007-07-26 20:29:03 UTC

Changes similar to the patch attached to this bug have been checked in.  One
difference is that '-m MODNAME' does not imply '-p4'.