One unexpected bug

[gogo9th]

I found one bug in Jalangi2. If I run my test JS file Google.ca.js with my analysis-statement.js with the following command:

$ node src/js/commands/jalangi.js --inlineIID --inlineSource --analysis analysis-statements.js node-ok/Google.ca.js

, the program crashes with "Maximum Call Stack Exceeded" error. This bug occurs if I call "iidToLocation()" function inside the analysis chain. I fixed the bug inside jalangi2-master/src/js/runtime/iidToLocation.js:

...
sandbox.iidToLocation = function (sid, iid) {
var ret, arr, gid=sid;
if (sandbox.smap) {
if (typeof sid === 'string' && sid.indexOf(':')>=0) {
sid = sid.split(':');
iid = Number/parseInt/(sid[1]);
sid = Number/parseInt/(sid[0]);
...

If you parse integegers with parseInt() function, after a certain point Jalangi2 recursively calls iidToLocation() instead of proceeding to the code following the parseInt() call. This problem goes away if I replace parseInt to Number.