You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am trying to use this tool to generate call graphs for node.js packages, however, I find a parsing logic error from your tool. Here is my example:
define(function (require, exports) {
var test = {
keys: ()=>(console.log(a))
}
var x = {
keys: () => (console.log(b))
}
test.keys();
x.keys();
var c = 9;
Object.keys(c);
});
When parsing this js file, it seems the dftc algorithm didn't handle cases like property name for different objects. In this case, when function visit1 in dftc.js finds calls for keys of test, it firstly find the expression of func, then prop of 'keys', while here is only use the 'keys' to match call expressions, and finally, the call graph contains calls that from line 8,9,11 to both test.keys and x.keys, 6 calls in total.
The text was updated successfully, but these errors were encountered:
Hi, I am trying to use this tool to generate call graphs for node.js packages, however, I find a parsing logic error from your tool. Here is my example:
When parsing this js file, it seems the dftc algorithm didn't handle cases like property name for different objects. In this case, when
function visit1
indftc.js
finds calls forkeys
of test, it firstly find the expression of func, then prop of 'keys', while here is only use the 'keys' to match call expressions, and finally, the call graph contains calls that from line 8,9,11 to bothtest.keys
andx.keys
, 6 calls in total.The text was updated successfully, but these errors were encountered: