Bug 10495 - Allow multiple, same name, probe point alias alternatives
Summary: Allow multiple, same name, probe point alias alternatives
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-07 09:18 UTC by Mark Wielaard
Modified: 2009-08-19 00:16 UTC (History)
0 users

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 Mark Wielaard 2009-08-07 09:18:05 UTC
Currently the following isn't allowed:

probe memory_hog = process("alpha").function("allocated_huge") ?
{
  hogger = "alpha";
}

probe memory_hog = process("beta").function("allocated_giant") ?
{
  hogger = "beta";
}

semantic error: duplicate probe point pattern while registering probe alias
memory_hog = process("beta").function("allocated_giant")

You could write it as:

probe memory_hog = process("a").function("alpha") ?,
                   process("beta").function("allocated_giant") ?
{
  hogger = "alpha or beta";
}

But that has two drawbacks. First you cannot easily set the hogger variable.
Second you cannot use this pattern if your tapset is split over multiple files.
Comment 1 Frank Ch. Eigler 2009-08-19 00:16:01 UTC
commit 2531fc1

Quite possibly, some existing tapsets could make use of this.