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, first of all, thank you for open-sourcing your datasets!
I have a problem with the call graph data and am wondering how to handle it. Some lines in the CallGraph CSV files contain 12 columns instead of 11. From what I have seen, the problem always stems from the fact that there is more than one rpcId and the rpcIds are delimited via a comma, which is also the delimiter used for columns in the CSV file. This causes exceptions when trying to read the files with the pandas library.
Are the multiple rpcIds intentional? And if so, why is it that sometimes there are two equal rpcIds? Here is an example from CallGraph_0.csv where 0.1.1.1 is present twice:
Hi, first of all, thank you for open-sourcing your datasets!
I have a problem with the call graph data and am wondering how to handle it. Some lines in the CallGraph CSV files contain 12 columns instead of 11. From what I have seen, the problem always stems from the fact that there is more than one rpcId and the rpcIds are delimited via a comma, which is also the delimiter used for columns in the CSV file. This causes exceptions when trying to read the files with the pandas library.
Are the multiple rpcIds intentional? And if so, why is it that sometimes there are two equal rpcIds? Here is an example from
CallGraph_0.csv
where0.1.1.1
is present twice:175636,T_20587044318,S_98992619,0.1.1.1,0.1.1.1,rpc,UNKNOWN,UNKNOWN_POD_6387478,i2--iNwFiz,MS_56 ...
The text was updated successfully, but these errors were encountered: