public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Lewandowski <k.lewandowsk@samsung.com>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GCOV doesn't seem to work on ARM with kernel 2.6.35-rc6
Date: Tue, 27 Jul 2010 09:35:08 +0200	[thread overview]
Message-ID: <4C4E8C2C.3000903@samsung.com> (raw)
In-Reply-To: <4C4DBE8E.70102@linux.vnet.ibm.com>

On 07/26/2010 06:57 PM, Peter Oberparleiter wrote:
> Karol Lewandowski wrote:
>> On 07/26/2010 12:32 PM, Karol Lewandowski wrote:
>>> 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 just tested gcov support for 2.6.35-rc6 on s390 and it works without
> a problem. My assumption would be that you are using an EABI-GCC to
> compile your kernel. Those compilers name their constructor symbols

Exactly.

> differently than the vanilla GCC so that the whole constructor calling
> mechanism on which the gcov support relies, will fail. If that is
> indeed the case, the following testing patch should solve your
> problem:

Yes, that was the case and your patch indeed solved my problem.

Thank you very much for your help!

  reply	other threads:[~2010-07-27  7:35 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
2010-07-26 16:57   ` Peter Oberparleiter
2010-07-27  7:35     ` Karol Lewandowski [this message]
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=4C4E8C2C.3000903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox