Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <holger+oe@freyther.de>
To: Steffen Sledz <sledz@dresearch.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: profiling howto?
Date: Thu, 03 Feb 2011 13:14:40 +0100	[thread overview]
Message-ID: <4D4A9C30.8010803@freyther.de> (raw)
In-Reply-To: <4D4A9A94.6030108@dresearch.de>

On 02/03/2011 01:07 PM, Steffen Sledz wrote:

> But i've no idea what the real problem is. It looks like it's not related to the ".init_array" but to the missing `mcount' symbol.

This symbol access get added by gcc due the -pg option. Now the question is
who should provide this symbol? I would assume it is glibc (actually grepping
glibc source tree shows it is in gmon/mcount.c).

I am not sure why you want to use gprof but anyway...

a) do not use gprof on glibc...
b) change the tests to have a mcount symbol...
c) more options here.



  reply	other threads:[~2011-02-03 12:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  9:54 profiling howto? Steffen Sledz
2011-02-02 10:11 ` Holger Freyther
2011-02-02 11:12   ` Henning Heinold
2011-02-02 12:59 ` Steffen Sledz
2011-02-02 13:12   ` Holger Freyther
2011-02-03  8:05     ` Steffen Sledz
2011-02-03  9:00       ` Holger Freyther
2011-02-03 10:44         ` Steffen Sledz
2011-02-03  8:30   ` Steffen Sledz
2011-02-03  8:54     ` Jan Paesmans
2011-02-03 10:52       ` Steffen Sledz
2011-02-03 11:30         ` Holger Freyther
2011-02-03 11:50           ` Steffen Sledz
2011-02-03 11:53             ` Holger Freyther
2011-02-03 12:07               ` Steffen Sledz
2011-02-03 12:14                 ` Holger Freyther [this message]
2011-02-03 13:06                   ` Steffen Sledz
2011-02-03 13:10                     ` Holger Freyther
2011-02-04 12:09                       ` Steffen Sledz
2011-02-03 14:25                 ` Phil Blundell
     [not found]                 ` <1296735116.2258.44.camel@phil-desktop>
2011-02-03 14:25                   ` Phil Blundell
2011-02-03 22:34                     ` Khem Raj

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=4D4A9C30.8010803@freyther.de \
    --to=holger+oe@freyther.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=sledz@dresearch.de \
    /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