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
{{ message }}
Repository navigation
Phasar does not support exit() as exit points when calling getAllExitPoints() #728
Hi @yuffon,
this is actually intended behavior. We use getAllExitPoints (and isExitInst) to get the locations from where data flows have to be mapped back to the callers. This happens for ret and resume instructions. For exit(), abort() and others the program ends more or less immediately and data-flows will never reach the callers from there.
I see that the naming is confusing. Maybe, we can add another function that covers these cases as well.
Hi @yuffon, this is actually intended behavior. We use getAllExitPoints (and isExitInst) to get the locations from where data flows have to be mapped back to the callers. This happens for ret and resume instructions. For exit(), abort() and others the program ends more or less immediately and data-flows will never reach the callers from there. I see that the naming is confusing. Maybe, we can add another function that covers these cases as well.
OK. Thanks. I need to get all exit points of main function for seed facts in backward dataflow analysis.
Activity
fabianbs96 commentedon Jun 30, 2024
Hi @yuffon,
this is actually intended behavior. We use getAllExitPoints (and isExitInst) to get the locations from where data flows have to be mapped back to the callers. This happens for
retandresumeinstructions. Forexit(),abort()and others the program ends more or less immediately and data-flows will never reach the callers from there.I see that the naming is confusing. Maybe, we can add another function that covers these cases as well.
yuffon commentedon Jul 2, 2024
OK. Thanks. I need to get all exit points of main function for seed facts in backward dataflow analysis.