]> sourceware.org Git - systemtap.git/commit
make from_glob a per-component field rather than per-pp
authorJonathan Lebon <jlebon@redhat.com>
Thu, 14 May 2015 14:29:50 +0000 (10:29 -0400)
committerJonathan Lebon <jlebon@redhat.com>
Thu, 14 May 2015 14:51:56 +0000 (10:51 -0400)
commitd2eaa03ba08e5672f11de5263b73fb3acd13b792
treeb7113ad44ba9a83d48551b73747ebbf9351c4281
parent3237a9d72205e9afba9d4930c799a860be77d21d
make from_glob a per-component field rather than per-pp

The original need for from_glob in probe_point was to distinguish
"specified" probe points from those that were still generic/globby. E.g.
so that we know to make function suggestions for
process("/usr/bin/ls").function("bad_func") but not yet for
process("/usr/bin/l*").function("bad_func").

The issue however is that there is no distinction between which
component is from a globby one. E.g. if we have
process("/usr/bin/l*").library("libc").function("bad_func"), which
becomes process("/usr/bin/ls").library("libc").function("bad_func"), we
won't know while resolving the library whether from_glob is true because
the process was globby or because the library was globby.

Thus, the 'from_globbiness' is a property of the component, not the
whole probe point. In this commit, we make from_glob instead a member of
probe_point::component. We then add a from_globby_comp() function which
can be used to determine if a specific component was derived from a
globby one.
elaborate.cxx
staptree.cxx
staptree.h
tapset-mark.cxx
tapsets.cxx
This page took 0.027615 seconds and 5 git commands to generate.