public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Ringo Pebam <ringo_pebam@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Gcov for user level application
Date: Tue, 02 Aug 2005 17:02:00 -0000	[thread overview]
Message-ID: <42EFA713.8050305@codesourcery.com> (raw)
In-Reply-To: <20050719065454.88596.qmail@web50008.mail.yahoo.com>

Ringo Pebam wrote:
> Hi,
> 
> I compile my user level application code on my host machine with the appropiate
> cross compiler.
> 
> It generates the .bb and .bbg files plus the executable.
> 
> I transfer these 3 files to the target device and there i tried running the 
> executable, hoping to get the .da file. But it is not generated.

you only need the exectuable on the target.  It should produce the .da file 
whetehr or not the other files are there.  Can your target write to a file?

> I thought the kernel running on the target(arm9 processor) doesnt supports gcov 
> for user level application, and went to makemenuconfig, there the option is only 
> for kernel and not user level applications.

this is not a kernel feature.

> 
> Could you please suggest me how should make Gcov work on my target device ??
> 
> I am thinking of cross compiling the gcov source and put it on the target 
> device. Could anybody tell me where i could find the gcov source code ?

It sounds like the target cannot create files on the file system.  That would be 
a libc issue.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

      reply	other threads:[~2005-08-02 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  6:55 Ringo Pebam
2005-08-02 17:02 ` Nathan Sidwell [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=42EFA713.8050305@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ringo_pebam@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).