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]

Re: user instruction tracing patch?


On Fri, 2007-11-16 at 15:37 -0500, Frank Ch. Eigler wrote:
> Hi -
> 
> On Fri, Nov 16, 2007 at 01:20:51PM -0800, Jim Keniston wrote:
> > [...]
> > But what both examples assume is that a task can dynamically
> > enable/disable probes only for itself (in the case of utrace/itrace)
> > or its own process (uprobes).
> 
> Not at all - the script fragments were merely examples of a general
> syntax.  There is no reason that the probes being enabled/disabled
> might not belong to an altogether "foreign" facility such as a timer,
> or a kprobe, or another process's uprobe.  (This one reason why the
> implementation of disableable probes will be a bit tricky.)

Sorry, I still don't get it then.  Given
	probe program("/bin/vi").function("malloc") if (mp) { .. }
if some handler executes
	mp = 1;
how does stap know which instance(s) of vi to probe?

> 
> 
> - FChE

Jim


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