Re: [Valgrind-users] cannot figure out callgrind --zero-before function names (C++)

[Josef W. <Jos...@gm...>]

Correcting myself...

On Monday 27 September 2010, Josef Weidendorfer wrote:
> On Saturday 25 September 2010, Mike Coleman wrote:
> > Hadn't seen the wildcard thing documented anywhere.
> 
> Ooops.
> This should get a top priority on my TODO list. Thanks for pointing out.
> It works like shell globbing, with wildcards "*" (0 or more unknown chars)
> and "?" (exactly one unknown char).

This *is* documented in the Callgrind manual, see

   http://valgrind.org/docs/manual/cl-manual.html


In 6.2.1 under "Dumping at enter/leave of specified functions": 

"Function specifications support wildcards: e.g. use --dump-before='foo*' to
generate dumps before entering any function starting with foo."

In 6.3. "Callgrind Command-line Options":

"Some options allow the specification of a function/symbol name, such
as --dump-before=function, or --fn-skip=function. All these options can
be specified multiple times for different functions. In addition, the
function specifications actually are patterns by supporting the use of
wildcards '*' (zero or more arbitrary characters) and '?' (exactly one
arbitrary character), similar to file name globbing in the shell. This
feature is important especially for C++, as without wildcard usage, the
function would have to be specified in full extent, including parameter
signature."



Where did you expect the documentation of wildcards in addition to the above?

Josef