From: "McLendon, Rodney" <Rodney.McLendon@amd.com>
To: gcc-help@gcc.gnu.org
Subject: gcov-kernel patch
Date: Fri, 02 Jun 2006 23:53:00 -0000 [thread overview]
Message-ID: <C3946CD6D455964280163B82031D3954027BE13C@SAUSEXMB2.amd.com> (raw)
Hi,
I am trying to use the gcov-kernel patch that allows for the relocation of the source based on the environmental variables GCOV_PREFIX and GCOV_PREFIX_STRIP. The problem that I am having is that the environmental variables don't seem to have any effect in relocating the source when processing or generating the .gcda files. The following sort of depicts my configuration:
Sys A: cross-compiled source in path /home/user/tmp/work/linux-2.6.16/... for
Sys B, producing .gcno files
Sys B: generates the .gcda files (I set GCOV_PREFIX_STRIP=4 here but had no
effect)
Sys C: (inside /somedir which contains linux-2.6.16, a directory that now
contains the source as well as both .gcno and .gcda files) executed
'lcov -c -o somefile.info -d linux-2.6.16' here and produced an error
that indicated it could not find my source in
/home/user/tmp/linux-2.6.16/... although once again I set
GCOV_PREFIX_STRIP=4.
On which system should the environmental variable(s) be set/used?
Thanks,
Rodney
reply other threads:[~2006-06-02 23:53 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=C3946CD6D455964280163B82031D3954027BE13C@SAUSEXMB2.amd.com \
--to=rodney.mclendon@amd.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).