activate

Right click project and select properties

Select C Coverage category and turn on the Activate nature checkbox

compiler option settings

Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage -std=c99 " compiler option

linker option settings

Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage -std=c99 " linker option

Rebuild your project.

run

Run the binary and executed lines and never executed lines are highlighted as can be seen in below screenshot. * Note: if the high lighted code does not show, you should select refresh project

Problems

Possibility to use an external tools (for me it's an external make target) that will execute gcov. (http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)

Solutions

Coverage builder and the coverage result extraction should be separated using Builder for gcov execution and Error parser to retrieve result of coverage. Error parser can start retrieve result of coverage by external tools' gcov execution, like external make target or lcov(http://ltp.sourceforge.net/coverage/lcov.php). Gcov execution of Builder should be switch between enable and disable. Error parser can retrieve result of coverage alone,when Builder is set to disable.

Performance

Problems

In a Project with a lot of files, coverage calculation can takes a lot of time. Eclipse cannot be used until gcov builder is finished. (http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)

Solutions

• Add a stop operation that can stop Builder and Error parser.
• Add a mode that enable to start Builder and Error parser only by manually.
• Builder and Error parser should be background task not to effect GUI.
• To save gcov execution time, parsing *.gcno and *.gcda files directory.
• Make a enable Builder and Error parser per folder or source file

(http://sourceforge.jp/forum/forum.php?thread_id=22157&forum_id=13644)

Problems

The Builder file search is too slow, an other method should be used. (http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)

Solutions

• Find source file's path from *.gcno or *.gcda file

User Interface

Solutions

Like for subversion plug-in it should be good to have coverage information display directly on Project Explorer view (not in an other view).

Others

• support branch coverage
• coverage history

Welcome to the "CDT gcov plugin" project Wiki Pages.

This Wiki is intended for users & developers. All pages can be edited by anyone. You can try out in SandBox.

Project Summary

The "CDT gcov plugin" is a free C/C++ code coverage tool for Eclipse, available under the Eclipse Public License. At the moment, it supports statement coverage. Requirements include the Eclipse CDT and gnu gcov.

Download

Archived version：

https://sourceforge.jp/projects/ginkgo/files/

Eclipse update site:

http://svn.sourceforge.jp/svnroot/ginkgo/trunk/org.ginko.gcov.update/

Screenshots

C project

C++ project

Usage

Information on setting up the plug-in can be found in this short guide.

License

Eclipse Public License, see:

http://www.eclipse.org/legal/epl-v10.html

Tested Programming Environments

OK

• centOS 4.4
• windows xp(cygwin gcc)
• unbutu 7.4
• unbutu 7.4 on VMWare

NG

• windows xp(cygwin gcc -mno-cygwin option)

The problem is that -mno-cygwin does not work with gcov
reference http://www.cygwin.com/ml/cygwin/2007-11/msg00180.html

Feature Plan

• Feature Plan
• support for branch coverage
• coverage history

Pages For Developers

• subversion access
• internal release

svn+ssh://svn.sourceforge.jp/svnroot/ginkgo

1. Upload your ssh's public key to the sourceforge.

For details,refer to the following address. https://sourceforge.jp/account/editsshkeys.php

2. Test your ssh connection.

$ ssh loginname@shell.sourceforge.jp

3. Configure git setting and clone the git repository at first time.

$ git config --global user.name "Your Name Comes Here"

$ git config --global user.email loginname@yourdomain.example.com

$ git clone loginname@git.sourceforge.jp:/gitroot/ginkgo/master.git

For details,refer to the following address.

https://sourceforge.jp/projects/ginkgo/info

4. Switch to the master branch.

$ cd master

$ git checkout master

5. Fetch from master repository's changes every time before you start tasks.

$ git-pull --rebase

6. Edit source code and commit to your local repository several times.

$ git commit -a -m "some commit message"

7. If your source code works well,commit to master repository.

$ git-pull --rebase

$ git push

oh ok ... check check

CDT gcov plugin のプロジェクト Wiki ページへようこそ。

ユーザー、開発者どなたでも自由に使って下さい。(どなたでも編集できます)

Wiki ってなに？という方は、 Wikipedia の「ウィキ」のページ を参考にしてください。

文法などのドキュメントは、サイドバーに標準で入っているリンクか、 SourceForge.jp プロジェクト内の Wikiガイド を 参照してください。

概要

CDT gcov pluginはEclipse 上で c 言語で書かれたコードのカバレッジを表示するオープンソースソフトウェアです。gcovとcdtを用い、行カバレッジをサポートします。

ダウンロード(download)

アーカイブ一覧：

https://sourceforge.jp/projects/ginkgo/files/

update site:

http://svn.sourceforge.jp/svnroot/ginkgo/trunk/org.ginko.gcov.update/

スクリーンショット(screen shot)

使用方法(How to use)

HowToUse

ライセンス(license)

eclipse public license

http://www.eclipse.org/legal/epl-v10.html

動作環境(environment)

OK

• centOS 4.4
• windows xp(cygwin)
• unbutu 7.4
• unbutu 7.4 on VMWare

NG

• windows xp(cygwin -mno-cygwin オプション)

cygwin上でのgcc -mno-cygwin オプションがgcovに対応していないため
http://www.cygwin.com/ml/cygwin/2007-11/msg00180.html を参照

計画(plan)

• 分岐網羅への対応(support for branch coverage)
• 実行履歴(coverage history)

開発者向け(for developer)

ForDeveloper

English

日本語

活性化

プロジェクト(project)からプロパティ(property)を選択
C CoverageからActivate natureのチェックボックスをオンに

コンパイラオプション設定

CDTのビルドセッティングのうちコンパイラのオプションに-fprofile-arcs -ftest-coverageを追加

リンカオプション設定

CDTのビルドセッティングのうちリンカのオプションに-fprofile-arcs -ftest-coverageを追加

実行

対象を実行するとカバレッジに応じた色が表示される
※更新されない場合はプロジェクトの更新(refresh)