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

Colorize head and tails basic blocks in function graph (graphviz) #90

Open
radare opened this issue Mar 30, 2016 · 5 comments
Open

Colorize head and tails basic blocks in function graph (graphviz) #90

radare opened this issue Mar 30, 2016 · 5 comments

Comments

@radare
Copy link

radare commented Mar 30, 2016

No description provided.

@ret2libc
Copy link

More details about this?

@radare
Copy link
Author

radare commented Mar 30, 2016

Nodes with no input edges are head , so we should colorize them as yellow for example.

The nodes with no output edges are considered end nodes, and can be painted as orange for example

On 31 Mar 2016, at 00:15, Riccardo Schirone notifications@github.com wrote:

More details about this?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

@ret2libc
Copy link

I see. I would put this thing as optional, with a key or a var. what did you think?

@radare
Copy link
Author

radare commented Mar 31, 2016

we can just define those colors as the same for the normal nodes by default, so it’s up for the user to change that. not sure if a toggle makes sense here

On 31 Mar 2016, at 08:47, Riccardo Schirone notifications@github.com wrote:

I see. I would put this thing as optional, with a key or a var. what did you think?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/radare/radare2/issues/4463#issuecomment-203786951

@ret2libc
Copy link

This issue has been moved from radareorg/radare2 to radareorg/ideas as we are trying to clean our backlog and this issue has probably been created a long while ago. This is an effort to help contributors understand what are the actionable items they can work on, prioritize issues better and help users find active/duplicated issues more easily. If this is not an enhancement/improvement/general idea but a bug, feel free to ask for re-transfer to main repo. Thanks for your understanding and contribution with this issue.

@ret2libc ret2libc transferred this issue from radareorg/radare2 Jun 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants