If I've understood you correctly, any tool that can build a (static) call
graph should suffice. Just that, you'll have to manually reverse trace paths
starting from function().

Do CMIIW...

On Fri, Aug 20, 2010 at 9:45 PM, George Kadianakis <desnacked@gmail.com>wrote:

> Greetings,
>
> I think I'm loosing faith in Emacs. It's the first time I'm looking
> for a tool and I don't get countless .el scripts with a trivial Google
> search.
>
> I'm looking for a tool (preferably an Emacs tool, but _seriously_
> anything will do) that will give me all possible code paths to a given
> function of a C project.
>
> For example:
> Input: (magic-script function)
> Output: 1) main() [main.c] -> function_1() [main.c] -> function_2() [oh.c]
> -> function_3() [oh.c] -> function_4() [ohlol.c] -> function() [yay.c]
>        2) main() [main.c] -> function_5() [yay.c] -> function_3() [oh.c] ->
> function_2() [oh.c] -> function() [yay.c]
>        3) etcetera
>
> GNU cflow is actually doing that _but_ it doesn't support multiple
> source files and it's not Emacs integrable.
>
> Do you people know of any such tools?
>
> Thank you :)
>
>