Michael Förderer
Michael Förderer
Duplicate of https://github.com/gcovr/gcovr/issues/583. This is a gcov bug and not related to gcovr.
In the linked issue this bug of gcov was discussed and the other issue is our workaround to ignore this bug. The workaround is only available on mater and will...
Oh, in the PR comment the option was wrong. Please use `--gcov-ignore-parse-errors=negative_hits.warn` or `--gcov-ignore-parse-errors=negative_hits.warn_once_per_file`. I'll update the PR description.
It makes a difference. The option is accepted but GCOV itself exits with 6. This is becuase the tool is executed in `/var/home` which is write protected. Can you change...
Because files are not found or can't be written by gov. Can you check the main branch?
In which directory was the compiler executed to build the object file? Can you try to run gcov on your own in this directory?
Can you execute the gcov command from the verbose output in this working directory and check the output?
Can you check the main branch?
@martinpitt Any updates with the latest version?
I can reproduce it but I don't get how meson is working. I found out that the compiler is executed in the directory `/tmp/umockdev/b`. But I'm wondering why gcc is...