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

Implementation of import graph #9867

Closed
guivc opened this Issue Apr 11, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@guivc

guivc commented Apr 11, 2018

I would call it import “graph” but i can think on other kind of graphs:

  • callgraph
  • xrefs graph
  • refs graph
  • bb graph
  • data graph

For example, graphing all references to local variables in a function by making variables and addresses where those are referenced as nodes.

Etc

All this stuff is easy to do, the only complicated part is defining a clean way to achieve all that and cleanup the ag* commands once again to make it more consistent
@radare (related to #9465)

@radare radare added this to the 2.6.0 milestone Apr 12, 2018

@radare radare added the question label Apr 12, 2018

@XVilka

This comment has been minimized.

Collaborator

XVilka commented Apr 25, 2018

@cyanpencil - kind of related to the graphs issues, regarding the consistency of ag commands.

@cyanpencil

This comment has been minimized.

Collaborator

cyanpencil commented Apr 25, 2018

Thank you for pointing this out to me.
Also, #8385 is related - maybe we can add them to #6967?

@radare

This comment has been minimized.

Owner

radare commented May 2, 2018

yeah, but as long as we can close this issue soon theres no need to do more issue management over engineering :)

@radare

This comment has been minimized.

Owner

radare commented May 21, 2018

This is done in master already. thanks @cyanpencil !

@radare radare closed this May 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment