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

[Feature Request]: Disable Instrumentation On-Demand #34

Open
magnus-madsen opened this issue Apr 16, 2015 · 2 comments
Open

[Feature Request]: Disable Instrumentation On-Demand #34

magnus-madsen opened this issue Apr 16, 2015 · 2 comments

Comments

@magnus-madsen
Copy link

In Jalangi it is currently possible to turn instrumentation on/off with a ENABLE_SAMPLING and runInstrumentedFunctionBody.

What I would like to ask for is a mechanism, for example as part of preFunInvoke, where you can opt to enter the original un-instrumented function and thus escape entirely to a world where nothing is instrumented. You would of course never be able to go back.

A potential issue is function objects stored in the heap, and how they would be replaced. Here it might still be sufficient to rely on the ENABLE_SAMPLING trick.

If this is beyond the scope of Jalangi, some pointers on how to achieve this would be welcome.

@magnus-madsen
Copy link
Author

I guess an important issue is that my proposal break identity of function objects and as such may change the semantics.

@ksen007
Copy link
Contributor

ksen007 commented Apr 20, 2015

this will create problem with closures.

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