Re: [RFC] New markers description without format strings

Hi -

On Mon, May 07, 2007 at 11:23:00AM -0400, Mathieu Desnoyers wrote:

> [...]  The difference is that I don't have to generate every
> combination of function names, which would result in a huge header
> file.

Indeed (for some definition of "huge").

> [...]  As long as systemtap does not use the arguments passed as
> parameter, I can understand this, but how does it expect to "know"
> what parameters a specific marker receives ?

The type signature string or enum is stored in the kernel binary.
We'd just pull it out of there during translation time and parse it
once.  Remember, we support cross-compiling, so likely we couldn't
call kernel APIs just to get a *list* of available markers and their
parameter types.

- FChE