All of lore.kernel.org
 help / color / mirror / Atom feed
From: Real Name <enjoymindful@gmail.com>
To: binutils@sourceware.org,
	user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] gprof missing functions
Date: Thu, 24 Jul 2014 16:16:18 +0800	[thread overview]
Message-ID: <20140724081618.GA1797@name> (raw)

hi,
  When trace the UML linux kernel with gprof, it seems gprof missing some
functions.

There are new_thread_handler and fork_handler in "arch/um/kernel/process.c".
gprof catchs the new_thread_handler function, but there is no sign about
fork_handler. Because the two functions are in the same file, so it is not
kernel configuration issue. I'm sure the two functions have been executed.

And new_thread_handler call a few functions, such as, kernel_init and kthreadd.
gprof catch kthreadd but missing kernel_init. I traced the UML kernel with gdb,
so I'm sure kernel_init called by new_thread_handler.

I search with google, but failed to get useful information about gprof missing
function issue. Is there any clue/suggestion how to make gprof catch all functions?

thanks

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


                 reply	other threads:[~2014-07-24  8:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140724081618.GA1797@name \
    --to=enjoymindful@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.