Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vararg treatment #8

Open
dweinstein opened this issue Feb 8, 2018 · 1 comment
Open

vararg treatment #8

dweinstein opened this issue Feb 8, 2018 · 1 comment

Comments

@dweinstein
Copy link
Member

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

@oleavr
Copy link
Member

oleavr commented Feb 8, 2018

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 printf format strings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants