automated callgraph creation

[Onkar Shinde]

It would be a very useful feature if there was a way to have a callgraph created automatically, especially when working with unfamiliar assembly source code, this could help understand the source code structure.

[Bug Importer (bug-importer)]

If this is implemented it would also be useful if there was a way to obtain information about:
- global data that is modified by a function
- input registers/memory that is used
- output registers/memory that is used

[Bug Importer (bug-importer)]

This seems like an extension to the current debugger code

[The Escapist (wisd00m)]

I think it would be possible to implement it like this:

1) add new tab
2) register a listener callback for all invocations of all "call" instructions
3) always store the IP for each insn
4) note down all register/stack access until a "ret" instruction is found