Bug #7585
closedDTrace probes are inconsistent
Description
These are DTrace probes available in Ruby:
process("./libruby.so").mark("find__require__entry") $arg1:long $arg2:long $arg3:long
process("./libruby.so").mark("find__require__return") $arg1:long $arg2:long $arg3:long
process("./libruby.so").mark("load__entry") $arg1:long $arg2:long $arg3:long
process("./libruby.so").mark("load__return") $arg1:long
process("./libruby.so").mark("require__entry") $arg1:long $arg2:long $arg3:long
process("./libruby.so").mark("require__return") $arg1:long
I am wondering, why find__require__return probe accepts more parameters then the load__return and require__return. They should all accept the same parameters IMO. No matter if they provide the source informations or not.
Also the remaining pair probes should be probably revisited and made consistent with the probes above:
process("./libruby.so").mark("cmethod__entry") $arg1:long $arg2:long $arg3:long $arg4:long
process("./libruby.so").mark("cmethod__return") $arg1:long $arg2:long $arg3:long $arg4:long
process("./libruby.so").mark("method__entry") $arg1:long $arg2:long $arg3:long $arg4:long
process("./libruby.so").mark("method__return") $arg1:long $arg2:long $arg3:long $arg4:long
process("./libruby.so").mark("parse__begin") $arg1:long $arg2:long
process("./libruby.so").mark("parse__end") $arg1:long $arg2:long