-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Idea] Instrumentation Framework #9
Comments
This mostly boils down to extending the hook capabilities, and then writing some statistics hooks right? |
yeah pretty much |
I added the |
I guess this doesn't really make sense since bf is so minimal. My initial thoughts were for this use case: you have a brainfuck program and you want to get certain statistics on its execution. You implement some hook functions, compile it into a shared object and then give that to the interpreter. Then at runtime, the interpreter loads the .so and calls those hooks at certain stages we support. |
I like the idea of playing with some dynamic loading of symbols. Good exercise. |
i think it could be cool to explore this idea of an instrumentation framework for bf. like being able to register callbacks not just after each step, but like before and after interpretation, before and after the instruction itself, on certain types of instructions, maybe even on ub. you could then use that to write analysis tools, for example
i'm basically thinking of doing something in the spirit of pin (https://software.intel.com/en-us/articles/pin-a-dynamic-binary-instrumentation-tool)
The text was updated successfully, but these errors were encountered: