Closed matjin closed 2 years ago
Fair enough, we should make sure this doesn't crash! I'm curious why it does though: what this does is dereference the address of formal parameters to get to their values in order to compute the initial state of the analysis of the current function. This should be uncontroversial and not result in an error to report to the user. I'll see how I can silence this but would love to debug it further if you have more information.
OK! I will follow up with the debug output :)
Should be fixed by 02a784948f4aa629234362c258bc2bfa01f6f3ad
Hello -- it seems that modifications made during April 2022 to PulseTaintOperations seem to be causing the analysis to crash in certain scenarios. Below is the stack trace. I did check out commit 2e1119932b895ad126faa4f56799d59cc3b34697 from March 31 and reran my example to validate that the crash does not occur on that version. Would it be possible to add some kind of exception handling to PulseTaintOperations to prevent this issue from resulting in analysis crash?