> "... DTrace requires that each probe clause produce a fixed-length trace > record. This means that the total number of bytes generated by all of > the recording actions (trace, printf, etc.), for one clause, must be > constant. Each clause can generate a different size record, but one > clause must generate the same size record each time it is invoked. If > the designers allowed flow control statements, the size of the trace > record could vary, depending on whether the if condition was true."
> Chip Is this really true (that clauses cause different-sized records)? Why don't you simply, automatically null (or space) pad the trace record of the smaller if condition(s)? Or, in the case of user-based functions (which could also screw up this requirement) require that the user pass an argument to the his/her function indicating how many bytes that it will return? Paul -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list [email protected]
