User forums > Using Code::Blocks

How can I display a call-tree?

(1/1)

TDuell:
Hullo All,
I am new to CodeBlocks, so this might be a silly question.
I am trying to get an understanding of an (old) unmaintained C project, and need to understand the overall structure.
Is it possible to get a graphical display of the what calls what...I think that is known as a call tree.

Ceniza:
Nope, at least not with Code::Blocks.

Jenna:
The nearest thing you can do with C::B is afaik opening the "Call stack" in debug mode.
If your program stops at a breakpoint you can see the functions that where called before reaching the breakpoint.
But it is in no way graphical and (of course) might show tons of system-calls.

To activate it, place a breakpoint, start debugging and if the execution stops chose "Debug -> Debugging windows -> Call stack".

Maybe this helps a little bit.

MortenMacFly:
FYI: I used Doxygen (www.doxygen.org) for similar purposes. In can create call graphs and caller graphs for you. A project is pretty simple to setup: Basically just adding files and enabling the "features" if you use the wizard.

TDuell:

--- Quote ---FYI: I used Doxygen (www.doxygen.org) for similar purposes. In can create call graphs and caller graphs for you. A project is pretty simple to setup: Basically just adding files and enabling the "features" if you use the wizard.
--- End quote ---

Thanks for that info.
I installed doxygen and doxywizard and set it to work. Cripes, it certainly generates a lot of data...about 200MB for my project.
There are so many graphical call trees that I am a bit overwhelmed by it all. I suspect that it has actually added to the complexity rather than reduced it!
I probably need to play about a tad with a much smaller project to see how to tailor the output of doxygen to suit my needs.

Thanks again for your help.

Navigation

[0] Message Index