From: andi.platschek@gmail.com (Andreas Platschek)
To: kernelnewbies@lists.kernelnewbies.org
Subject: call graph
Date: Sun, 21 Feb 2016 08:54:20 +0100 [thread overview]
Message-ID: <56C96D2C.9090002@gmail.com> (raw)
In-Reply-To: <CAGdaadYvhN7svCTnt-_Vqy1fnbEUySYRbBptVn1Ubek1B6ZSNA@mail.gmail.com>
Hi,
On 2016-02-20 19:24, Mulyadi Santosa wrote:
>
>
> On Sat, Feb 20, 2016 at 5:08 PM, masoud hematpour <mashemat@gmail.com
> <mailto:mashemat@gmail.com>> wrote:
>
>
> Hello all,
>
> I need to create call graph of memory management. Is there any tool.
> I found "cflow" but the output is not good enough. Can anyone help
> me in preparing?
> or I should prepare manually.
>
>
> Thank you
>
> Hi...
>
> Have you check CodeViz?
> http://www.csn.ul.ie/~mel/projects/codeviz/
> <http://www.csn.ul.ie/%7Emel/projects/codeviz/>
>
I just looked at codeviz 2 weeks ago, and I would recommend to use the
"alternative method" with ncc
(http://students.ceid.upatras.gr/~sxanth/ncc/) as it is a lot simpler to
set it up (no need for a patched
version of gcc, etc.) and it is able to traverse function pointers.
thx!
andi
> also check this blog entry:
> http://deferred.io/2015/10/27/visualizing-linux-kernel-call-graphs.html
>
> One advice: try to be more specific when generating call graph i.e
> graph of page in. Other wise, you might find yourself generating too
> complex graph
>
>
>
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com <http://the-hydra.blogspot.com>
> training: mulyaditraining.blogspot.com
> <http://mulyaditraining.blogspot.com>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2016-02-21 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 10:08 call graph masoud hematpour
2016-02-20 18:24 ` Mulyadi Santosa
2016-02-21 7:54 ` Andreas Platschek [this message]
2016-02-21 10:46 ` masoud hematpour
2016-02-21 15:27 ` Mulyadi Santosa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C96D2C.9090002@gmail.com \
--to=andi.platschek@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).