Bug 2067 - investigate whether/how module("foo").* for compiled-in foo
Summary: investigate whether/how module("foo").* for compiled-in foo
Status: RESOLVED DUPLICATE of bug 3887
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Reported: 2005-12-19 18:24 UTC by Frank Ch. Eigler
Modified: 2007-10-15 19:45 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Frank Ch. Eigler 2005-12-19 18:24:39 UTC
According to one report, they don't currently work.

One possibility is to export the CONFIG_* values to systemtap scripts as yet
another preprocessor predicate, so that a cunning user could use kernel. instead
of module("foo"). (assuming that even works.  A better way would be to make the
translator/elfutils understand module("foo") for both cases.
Comment 1 Roland McGrath 2005-12-19 21:02:01 UTC
In the kernel build process, each module is drawn from a subdirectory in the
source tree.  So one possibility is to define module-name matching to mean a
name wildcard on the CU name, which is the source file.
Comment 2 Frank Ch. Eigler 2007-10-15 19:45:56 UTC
explicit alternation is a good implementation tactic

*** This bug has been marked as a duplicate of 3887 ***