This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: odd behavior in stap statement probes with varied wildcards
- From: Jonathan Lebon <jlebon at redhat dot com>
- To: BR Chrisman <brchrisman at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Mon, 16 Mar 2015 13:14:19 -0400 (EDT)
- Subject: Re: odd behavior in stap statement probes with varied wildcards
- Authentication-results: sourceware.org; auth=none
- References: <CAN4=B2nVNsnNYmZm3R_6xau=YiHdJ2+f457nnEeuzBLoZRfqWw at mail dot gmail dot com>
> Description:
> statement("*@<file>:<line>") *doesn't* find the probe point
> statement("<function>@<file>:<line>") *does* find the probe point.
> statement("*@<file>:*") *does* find the probe point (grepped)
> statement("*@<file>:0,<line>") *does* find the probe point
> statement("*@<file>:<line>,<line>) *does* find the probe point
Hmm, I can't reproduce this here (it always finds the probe point).
Going from your "foo.h" hint, I also tried it on functions in header
files and it also found it regardless of the syntax.
If possible, can you reduce it to a simpler reproducible testcase?
Cheers,
Jonathan