Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326121

Summary:	Error when displaying coverage for a library
Product:	[Tools] Linux Tools	Reporter:	Xavier Raynaud <xavier.raynaud>
Component:	GCov	Assignee:	Xavier Raynaud <xraynaud>
Status:	CLOSED WONTFIX	QA Contact:	Xavier Raynaud <xavier.raynaud>
Severity:	normal
Priority:	P3	CC:	akurtakov
Version:	0.6
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Xavier Raynaud

2010-09-24 03:39:03 EDT

(On behalf of George Liu)

I’m developing a C++ library, and it’s tested by a cppunit test program.
I wanted to use gcov to check for the library’s code coverage, but is it currently supported?

I added the –fprofile-arcs and –ftest-coverage flags to both the library and the test program. What I can see is a beautiful chart showing me the test program’s coverage. But how do I see the coverage for my library code?

When I select a .gcno file, and prompted for the binary file name, selecting the library binary file will give me an error
An error has occurred when parsing the coverage data files :
Checksums don’t correspond for _XXXXXX


I can use the following command line to “see” the coverage data, file by file. However, I’m looking for a easier way, (with GUI) to help me navigate through. 

gcov -f Jmf.cpp -o . | c++filt > junk
vi junk

Comment 1 Andrew Overholt

2011-09-30 15:17:46 EDT

Updating Xavier's email address for existing bugs.

Comment 2 Alexander Kurtakov

2014-04-14 08:41:22 EDT

Is this still reproducible with latest versions?

Comment 3 Eclipse Genie

2016-04-04 12:12:53 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2018-03-26 11:39:58 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Eclipse Genie

2020-03-16 10:18:15 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Eclipse Genie

2022-03-07 10:27:51 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.