syscallx is not officially published (This was successfully run on a TL3 system). Without an associative array / aggregations, this wildcard capability is of little use. At best we can only gather basic statistical info (such as the number of syscalls for this PID, or time spent in each syscall, etc..). We will not be able to dump this into an aggregation and sort by the number of syscalls, or time spent in each syscall, etcÉ Although, it is possible we could do this with some post processing tool like perl.

syscallx does not support an actual REGEX capability in the probe point definition. I was able to do a (simplified) REGEX using the following code:

@@syscallx:$__CPID:*:entry

{

   funcname = get_function();

   if(strstr(funcname, ÓSIMPLE_PATTERN"))

      printf("%s\n", get_function());

}

I would argue that the power of syscallx (over syscall) is not the ability to wildcard the function name but the ability to probe significantly more syscalls than with the original provider.