Bug 11550 - dynamic probe point parameters
Summary: dynamic probe point parameters
Status: NEW
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on: 10995
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-28 11:52 UTC by Frank Ch. Eigler
Modified: 2012-06-13 20:53 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Ch. Eigler 2010-04-28 11:52:25 UTC
A request from IRC suggests a useful construct: where watchpoint probes'
addresses are computed on the fly.  Syntax could look like this:

global addr
probe kernel.data(addr).length(300) {  }
probe kernel.function("something") { addr = $myaddr }

so each time "something" hits, the address would be recomputed and the
hardware breakpoint probe reset.

This would require the same sorts of constraints on the globals as already
enforced for probe point conditionals.  This would also require the sorts
of on-the-fly registration/unregistration logic as pending for PR10995.

Some probe point types may permit such parametrization in several fields.
The dwarf ones would probably not support it in any slot, but
kprobe.function(SYM), timer.s(NN) could.