All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Lewandowski <k.lewandowsk@samsung.com>
To: Karol Lewandowski <k.lewandowsk@samsung.com>
Cc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: GCOV doesn't seem to work on ARM with kernel 2.6.35-rc6
Date: Mon, 26 Jul 2010 12:37:08 +0200	[thread overview]
Message-ID: <4C4D6554.30707@samsung.com> (raw)
In-Reply-To: <4C4D6458.6040402@samsung.com>

On 07/26/2010 12:32 PM, Karol Lewandowski wrote:
> Hello,
>
> I'm trying to use code coverage measurements with mainline Linux kernel
> 2.6.35-rc6 on ARM platform (specifically on Samsung's S5PC110 board).
>
> I've enabled following in my .config:
>
> CONFIG_GCOV_KERNEL=y
> CONFIG_DEBUG_FS=y
>
> After successful boot I see no gcov-related files other than
> /sys/kernel/debug/gcov/reset.
>
>  From my knowledge (and from my previous experience with out-of-tree
> gcov patchset) whole directory structure shall be created along with
> .gcda files and various symlinks.

I forgot to add that I've added "GCOV_PROFILE := y" to at least

   fs/Makefile
   kernel/Makefile

and few others.  Thus, I expect to find something more than just
./reset file.

  reply	other threads:[~2010-07-26 10:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 10:32 GCOV doesn't seem to work on ARM with kernel 2.6.35-rc6 Karol Lewandowski
2010-07-26 10:37 ` Karol Lewandowski [this message]
2010-07-26 16:57   ` Peter Oberparleiter
2010-07-27  7:35     ` Karol Lewandowski
2010-07-28 13:12       ` Peter Oberparleiter
2010-07-28 13:44         ` Karol Lewandowski
2010-07-28 15:57           ` Peter Oberparleiter
2010-07-29 16:25             ` Karol Lewandowski
2010-08-03  5:20               ` George G. Davis
2010-08-03  9:12                 ` Peter Oberparleiter

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=4C4D6554.30707@samsung.com \
    --to=k.lewandowsk@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oberpar@linux.vnet.ibm.com \
    /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.