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 (with dot) in calling order (Origin: bugzilla #641904) #4145

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity enhancement in component build for ---
Reported in version unspecified on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-02-09 07:06:52 +0000, raimund.stein@stahlcranes.com wrote:

Created attachment 180443
demo file for dot, with graphic

Hello doxygen,

an useful enhancement for me would be:
Arrangement of the call graph (with dot) in the (real) calling order in the calling function.

I tested with dot, with some little files, to see what is going to be produced.
I found, that the order in (my little) call graphs is the order the calls are arranged in the �source� (.dot) file.

In your dot-files, the nodes appear in an alphabetical order. If they were arranged in the calling order, dot should produce the call graph in the real sequence.
Attached you can find my little example: a dot file, and a graphic, generated with dot.
Dot.exe -Tpng aufruf3.dot -o aufruf3.png.

It is even possible, to have the same function called twice. Just have an extra Node with the same label. This could reflect very good the �real� usage of function-calls in (my) embedded software projects. There it is essential, in which order the functions are called, and also if they were called twice from the same calling function.

i´m actually using doxygen 1.7.1

On 2011-06-01 20:42:58 +0000, Dimitri van Heesch wrote:

I'll add the functions in order of first appearance to the dot graph.

On 2011-08-14 14:05:21 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

On 2011-09-15 10:51:05 +0000, Goffredo Marocchi wrote:

https://bugzilla.gnome.org/show_bug.cgi?id=657418

I think I am having this same problem or a very similar one. What do you think?

@doxygen doxygen closed this Jul 2, 2018

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