Manu Sridharan

Hi @gogo9th, to clarify, I was proposing to (optionally?) _remove_ usage of `arguments.callee` so that strict mode could be enabled. The main use of `arguments.callee` is to provide the function...

> I wonder what's an example of this. If we meet a native function, we will not track inside it anyway, so there will be no additional problem we need...

I came across a possible solution to this problem. In JS you can access the value of a function via its name. What if in Jalangi instrumentation, we introduced a...

@gogo9th thanks so much for all these great comments. Just an FYI that I am busy today and possibly tomorrow but I will give feedback here as soon as I...

@gogo9th: > I am very sorry for my late reply, I've found several more bugs/problems in Jalangi2 and have been fixing them. It took me about 100 hours, and I...

Tentatively I agree we can remove that callback that overwrites `arguments`. We should update the tests to pass if needed, and also document the change for the next release (and...

> I have one question. Why doe Jalangi wrap each script or function code with a while loop? What could go wrong if they are just wrapped by a try-catch...

For anyone still tracking this issue, I attempted to implement partial support for `use strict` here: https://github.com/Samsung/jalangi2/pull/175 It will fail at runtime for some unusual cases involving getters / setters....

@christofferqa can you also add a regression test for this issue?

@ksen007 reading #107 I think the issue is that Jalangi-instrumented code that might have worked in previous browser versions no longer works, due to changes in the browsers related to...