mwaldrich

I think it's also important to note that functionExit/invokeFun aren't sufficient for knowing what line of code returns. This is because try/finally blocks can execute code *after* an expression is...

Any update on this feature?

Thanks for the implementation! I'm starting to use this in my analysis now. I noticed this callback doesn't provide the *function* that the code is returning from. While it is...

Yes, it wouldn't make sense to model a callstack using the `_return` callback, because it does not signal the exiting of a function. But since I am trying to avoid...

Is there any update on this feature request? My team is hoping to use this feature soon.

Any update on this feature?

Ok, thanks for the work and the update!

Thanks for the implementation! We can now easily see the object involved with the loop. My team was planning on tracking how data flows into the loop variable. However, I'm...

I am confused about how the new callbacks could be used to instrument this. What callbacks would be generated in a single iteration of a for of loop? Also, would...

Sounds great! This should be enough to perform general instrumentation on async/await in JS. How much work will it be to clean up the hacky implementation and get it merged...