-
Notifications
You must be signed in to change notification settings - Fork 444
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
Call graph tree is not shown where there is just one called function #1868
Comments
|
What I report is — it does not draw a line showing that it is called from the
In current output it looks like |
Thanks for explanation though. Now (I think) I understand that tailing branch is just not indented to the right side. And it's meant that there is one branch going downwards. But that's a bit confusing (because there is no line downward). And looked like Same logic does not work inside of So while current representation is correct it's still harder to interpret because we cannot see downward lines (or their absence). On every occurrence of branching now user should think "is this following function call or nested function call with downward branch?" Perhaps this is not what user should be additionally thinking when they already try to understand logic of inspected binary |
I know it can be confusing. But I decided to do it that way to reduce the indention level for the simple, single call cases. Otherwise it would become hard to read after some depth. |
I hope I don't misunderstand usage, but call graph tree is not shown where there is just one called function, for example:
But it's shown when there is 2 functions:
The text was updated successfully, but these errors were encountered: