From: Richard Riley <rileyrg@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Call graph emacs tool
Date: Sat, 21 Aug 2010 03:50:07 +0200 [thread overview]
Message-ID: <i4nbch$bp2$1@dough.gmane.org> (raw)
In-Reply-To: 4C6F2E0F.3020607@gmail.com
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> On Friday 20 August 2010 09:15 AM, George Kadianakis wrote:
>> 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?
>
> I am not sure what you mean by all possible code paths to a function,
> but if you mean something like this,
> <http://i288.photobucket.com/albums/ll164/jalladandtux/screenies/emacs-symbol-reference-w-cedet.png>
What is that supposed to be? Is that a call stack?
next prev parent reply other threads:[~2010-08-21 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 16:15 Call graph emacs tool George Kadianakis
2010-08-21 1:38 ` Suvayu Ali
2010-08-21 1:50 ` Richard Riley [this message]
2010-08-21 3:04 ` Suvayu Ali
2010-08-21 3:13 ` Pranav Peshwe
2010-08-21 12:36 ` George Kadianakis
2010-08-21 16:18 ` Gary
2010-08-21 18:07 ` Suvayu Ali
[not found] ` <mailman.5.1282414155.26890.help-gnu-emacs@gnu.org>
2010-08-24 15:52 ` rustom
[not found] ` <mailman.0.1282394304.15763.help-gnu-emacs@gnu.org>
2010-08-21 15:35 ` rustom
-- strict thread matches above, loose matches on Subject: below --
2010-08-25 17:02 George Kadianakis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='i4nbch$bp2$1@dough.gmane.org' \
--to=rileyrg@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).