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
Thank you for your valuable work. We have read your paper with great interest; however, we encountered difficulties in applying the instrument you shared to a codebase other than the one you considered in your study.
Specifically, after:
setting up the environment where the tool should build, compile, and pass the kzalloc test as per the instructions in the README,
adding the following calls to the CallGraphMain function:
...We observed that the calls to the kmeld analyzer fail due to the absence of files such as run/releaseTerminals.txt, which do not appear to be generated anywhere in the repository.
Additionally, we noticed a potential issue in the Python code of the tool: the variable callSiteDict is used but does not appear to be defined anywhere.
Could you please provide guidance on how to resolve this issue?
Best regards,
Anton
The text was updated successfully, but these errors were encountered:
Dear colleagues,
Thank you for your valuable work. We have read your paper with great interest; however, we encountered difficulties in applying the instrument you shared to a codebase other than the one you considered in your study.
Specifically, after:
kzalloc
test as per the instructions in the README,CallGraphMain
function:...We observed that the calls to the kmeld analyzer fail due to the absence of files such as
run/releaseTerminals.txt
, which do not appear to be generated anywhere in the repository.Additionally, we noticed a potential issue in the Python code of the tool: the variable
callSiteDict
is used but does not appear to be defined anywhere.Could you please provide guidance on how to resolve this issue?
Best regards,
Anton
The text was updated successfully, but these errors were encountered: