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
The graph for each function entry now flows to a return node, except for a few tail call nodes that flow to a "None" node that is a sink. Looking at hooking those up to the return node.
I asked @danmatichuk (in Mattermost) if he could add the return info to the tail call nodes. No response yet. I committed a fix (fb5c224) that gets rid of spurious "None" CFAR nodes following "Tail Call" nodes. Now "Tail Call" nodes are sinks. As far as I can tell, the function return information is not in the data I get from the verifier for Tail Call nodes. If we want to link up the "Tail Call" nodes to the function return nodes, I need that data. What do others think?
great - thanks for the fix re: those None nodes! I'll let Dan chime in regarding whether there is more data available we want to wire in, but IMO tail calls as sinks in the PATE overview graph seems sufficient and lack of anything "beyond" it doesn't seem to negatively impact the operator's understanding of the GirdIDPS example at least
Once #388 is complete, make sure we see the synchronization/merge points we expect in the Binary Ninja UI for target7
The text was updated successfully, but these errors were encountered: