linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Lapin <slapinid@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: building of call tree
Date: Fri, 2 Apr 2010 20:16:59 +0400	[thread overview]
Message-ID: <k2u48239d391004020916w712535dala168de2a6d2b2bf7@mail.gmail.com> (raw)

Hi, all!

I'd like to make call-tree builder using libsparse.
I need to build symbol-hierarchy and feed dot with it.
I use test-dissect.c as an example.

I understand how to extract the symbols and find if it is definition
or reference,
but I fail with scoping. I need to detect which function that
particular reference belongs to,
and how to detect if that reference is really a function.
sym->type isn't what I need, sym->ctype.base_type is used to print base type,
but I'd like to print type as is, and detect if that is a function a proper way.
Or is there any better way to get this information?

Thanks a lot,
S.

             reply	other threads:[~2010-04-02 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 16:16 Sergey Lapin [this message]
2010-04-02 17:55 ` building of call tree Christopher Li

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=k2u48239d391004020916w712535dala168de2a6d2b2bf7@mail.gmail.com \
    --to=slapinid@gmail.com \
    --cc=linux-sparse@vger.kernel.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).