Skip to content

Coverage reporting hangs for C++ tests on X86 qemu #20729

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vanwinkeljan opened this issue Nov 15, 2019 · 3 comments
Closed

Coverage reporting hangs for C++ tests on X86 qemu #20729

vanwinkeljan opened this issue Nov 15, 2019 · 3 comments
Assignees
Labels
area: Test Framework Issues related not to a particular test, but to the framework instead bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale

Comments

@vanwinkeljan
Copy link
Member

Describe the bug

When C++ related tests are executed with coverage reporting on X86 Qemu, Qemu will end up in endless loop when dumping coverage results to UART.

To Reproduce

Steps to reproduce the behavior:

  1. Remove platform_exclude: qemu_x86_coverage from tests/application_development/libcxx/testcase.yaml
  2. sanitycheck -N -p qemu_x86_coverage -s tests/application_development/libcxx/misc.app_dev.libcxx

Expected behavior

C++ tests can run with coverage enabled on Qemu X86 without hanging.

Impact

No coverage reports can be generated for C++ test cases

Environment (please complete the following information):

  • OS: Linux - Ubuntu 18.04.3
  • Toolchain: Zephyr SDK 10.03
  • Commit SHA: 86461ac

Additional context

Quick look with gdb reveals that the while loop in gcov_coverage_dump is an endless loop

void gcov_coverage_dump(void)

@vanwinkeljan vanwinkeljan added the bug The issue is a bug, or the PR is fixing a bug label Nov 15, 2019
@dleach02 dleach02 added the priority: low Low impact/importance bug label Nov 19, 2019
@carlescufi carlescufi added the area: Test Framework Issues related not to a particular test, but to the framework instead label Apr 30, 2020
@carlescufi
Copy link
Member

@nashif any ideas about this one?

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Aug 15, 2020
@nashif
Copy link
Member

nashif commented Sep 10, 2020

well, we never got c++ code to work with coverage, Zephyr is all C and the intention of coverage is C code primarily, so closing. If someone has time, patches to support C++ code are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Test Framework Issues related not to a particular test, but to the framework instead bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Projects
None yet
Development

No branches or pull requests

4 participants