Skip to content
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

Gcov viewer Show command giving incorrect error message #34

Open
LK672 opened this issue Feb 4, 2025 · 2 comments
Open

Gcov viewer Show command giving incorrect error message #34

LK672 opened this issue Feb 4, 2025 · 2 comments

Comments

@LK672
Copy link

LK672 commented Feb 4, 2025

Hi! I was trying to use the gcov view Show command exactly as in the following video: https://www.youtube.com/watch?v=g3yJhl5q5_g. However, every time I run the gcov viewer command I get the following error

"The gcov version is not compatible. Please use at least version 9."

However, when I run gcc --version in terminal it says

"Apple clang version 16.0.0 (clang-1600.0.26.6)"

and similarly when running gcov --version and g++ --version terminal also outputs version 16.0.0 which is well above version 9.

Is there something I am missing here or is the error indicating something else. Thanks!

@JacquesLucke
Copy link
Owner

What's a bit confusing is that your gcc --version outputs something related to clang. Sounds like you are not using gcc after all. Note that the coverage format generated by clang is not compatible with this extension currently, at least it was not last time I tried.

@LK672
Copy link
Author

LK672 commented Feb 4, 2025

That makes sense. I brew installed gcc so now I compiled with gcc-14. For reference this is the output I get when I do gcc-14 --version

"gcc-14 (Homebrew GCC 14.2.0_1) 14.2.0"

(It does say Homebrew GCC but I am not sure if that makes a difference)

However, I am still getting the same error message as before. I tried setting alias gcov=gcov-14 in ~/.zshenv so that any usage of gcov would go to the homebrew gcc version instead of clang or LLVM but it seems to still be erroring in the same way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants