frida-trace
frida-trace copied to clipboard
vararg treatment
Any thoughts on treatment for variable argument functions? Seems like that would throw a wrench into things a bit. Just curious if you see a short path to that @oleavr
I've been thinking about it but it's not yet clear exactly how to implement this, except perhaps:
- Let the frida-trace API consumer provide a function to parse the argument list.
- Introduce a new top-level module in npm that implements an iterator-style API to fetch the next argument of a given type. This will involve ABI and architecture-specific knowledge, and given how complex this is it would be nice to also be able to use it from hooks written by hand, i.e. not using frida-trace. It should probably also provide helpers for parsing
printfformat strings.