Summary: The biabduction backend can raise exceptions that will be caught when triggered from within the biabduction backend itself (eg, `analyze_procedure` called from Symexec as a result of an ondemand analysis, because Symexec will catch these), but not caught when called as the result of an ondemand analysis emanating from another analyzer (eg ThreadSafety). Make the biabduction more self-contained by wrapping the analysis of a procedure inside a `try/with` with similar properties as the one of Symexec. Reviewed By: jeremydubreil Differential Revision: D5986335 fbshipit-source-id: 36a5d32master
parent
810d756f79
commit
da8333718a
Loading…
Reference in new issue