Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

binja: Check for missing sync in target7 #389

Closed
thebendavis opened this issue May 24, 2024 · 4 comments
Closed

binja: Check for missing sync in target7 #389

thebendavis opened this issue May 24, 2024 · 4 comments
Assignees

Comments

@thebendavis
Copy link
Member

Once #388 is complete, make sure we see the synchronization/merge points we expect in the Binary Ninja UI for target7

@thebendavis thebendavis added this to the May 2024 PI Meeting milestone May 24, 2024
@jim-carciofini jim-carciofini self-assigned this May 24, 2024
@jim-carciofini
Copy link
Contributor

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.

@jim-carciofini
Copy link
Contributor

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?

@jim-carciofini
Copy link
Contributor

Ben commented in Mattermost:

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

@thebendavis
Copy link
Member Author

Closing - in an offline discussion we determined that with these recent fixes we are now satisfied with the rendering of tail calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants