public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Pramendra Singh <Pramendra.Singh@lntinfotech.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] not able to generate HTML output
Date: Thu, 18 Feb 2010 15:44:40 +0530	[thread overview]
Message-ID: <20100218101440.GA21750@rishikesh.in.ibm.com> (raw)
In-Reply-To: <EB1A7C66AD0C92419BFFC785A947865A09EAE44689@BLRINMSMBX01.bglrodc.lntinfotech.com>

Hi Pramendra,
Can you let us know on which kernel/distro you are trying to take coverage ?

Thanks
Rishikesh

On Thu, Feb 18, 2010 at 12:30:03PM +0530, Pramendra Singh wrote:
> Hi everyone,
> 
> Good afternoon!
> 
> I am new to LTP and using it to test my code for PPC architecture.
> I have patched my kernel with GCOV and it seems working fine. But
> I  am not able to get the HTML of code coverage/
> 
> I am cross compiling the kernel on my server for PPC and putting the image
> to my PPC target board. After test I am able to get .gcda file for my .c file
> and I take it back to my server where my kernel  source is there.
> 
> I use ppc_85xx-gcov for generating coverage and after that I use
> "geninfo "  utiliy available in lcov-1.8 but I get error "not able to open
> Basic block .bb files."
> 
> Problem is that in my source code there is no .bb files but .gcno files are there
> and I think that is because my gcc compiler version is  3.4.1 but "geninfo" binary
> is compiled with some low version gcc.
> 
> So please let me know where to get source code for geninfo and genhtml so
> That I can compile them for  PPC architecture with my gcc version.
> 
> Or let me know if I am doing anything wrong is code coverage process.
> 
> Thanks in advance!
> 
> Thanks and Regards
> Pramendra Singh (Sr. Software Engg)
> L&T  InfoTech Ltd, Plot No # 25 ~31
> EPIP 2nd Phase, KIADB, Whitefield,
> Bangalore - 560066, Phone: 080-66242424, Extn: 2106,
> Mobile No:  9449718250
> 
> 
> 
> ________________________________
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
> 
> ______________________________________________________________________

> ------------------------------------------------------------------------------
> Download Intel&reg; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs 
> proactively, and fine-tune applications for parallel performance. 
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev

> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
Download Intel&reg; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs 
proactively, and fine-tune applications for parallel performance. 
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2010-02-18 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  7:00 [LTP] not able to generate HTML output Pramendra Singh
2010-02-18 10:14 ` Rishikesh K Rajak [this message]
     [not found]   ` <EB1A7C66AD0C92419BFFC785A947865A09EAE448A4@BLRINMSMBX01.bglrodc.lntinfotech.com>
2010-02-18 10:47     ` Rishikesh K Rajak
2010-02-18 19:42       ` 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=20100218101440.GA21750@rishikesh.in.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=Pramendra.Singh@lntinfotech.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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