From: Robert Berger <gmane@reliableembeddedsystems.com>
To: linux-kernel <linux-kernel@vger.kernel.org>, linux-arm@vger.kernel.org
Subject: gcov/lkm/arm-eabi/gcc 4.7.2 issue
Date: Tue, 12 Feb 2013 19:43:07 +0200 [thread overview]
Message-ID: <511A7F2B.20308@reliableembeddedsystems.com> (raw)
In-Reply-To: <20120530203428.GB16686@redhat.com>
Hi,
There seems to be an issue with gcov on kernel modules if you have an
arm-eabi gcc on Linux 3.8-rc6 and previous versions.
./arm-linux-gnueabi-gcc --version
arm-linux-gnueabi-gcc (GCC) 4.7.2
I followed these instructions [1], but without much success.
In case I compile an out of tree kernel module with gcov enabled it can
not be loaded and issues the following error: "unknown relocation: 38"
I tried this patch [2] as well without success. It loads now, but still
nothing useful in /sys/kernel/debug/gcov
Please advise,
Regards,
Robert
[1]
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=blob;f=Documentation/gcov.txt;h=e7ca6478cd93d4e6422d1ae92455b347dbdf7ccb;hb=HEAD
[2]
http://us.generation-nt.com/answer/add-gcov-support-arm-help-207630451.html
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
..."C treats you like a consenting adult. Pascal treats you like a
naughty child. Ada treats you like a criminal." -- (Bruce Powel Douglass)
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
prev parent reply other threads:[~2013-02-12 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 23:31 include/linux/dynamic_debug.h:111:2: error: implicit declaration of function ‘strstr’ shawn
2012-05-30 1:11 ` Jim Cromie
2012-05-30 1:43 ` shawn
2012-05-30 8:35 ` Jim Cromie
[not found] ` <1338387021.23168.18.camel@shawn-ssd>
[not found] ` <CAJfuBxxkMJbmvQMCZx=6GUqJ8c6VnT8jaRTKA-OWZLa0gG7kUw@mail.gmail.com>
2012-05-30 19:40 ` shawn
2012-05-30 20:34 ` Jason Baron
2012-05-30 20:51 ` shawn
2013-02-12 17:43 ` Robert Berger [this message]
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=511A7F2B.20308@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=linux-arm@vger.kernel.org \
--cc=linux-kernel@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