Markus Böck

I do not think this is currently possible. I have two ideas of solving this. Having a button to import coverage data manually and a task one can add to...

This is caused by this line: https://github.com/zero9178/C-Cpp-Coverage-for-CLion/blob/066cbcec99267b79c46fb16d896786a3ab542a70/src/main/kotlin/net/zero9178/cov/data/LLVMCoverageGenerator.kt#L167 funcStart is returning -1 which means that when trying to calculate branch coverage it somehow didn't find the function. This could be caused...

[C C++ Coverage-2019.2.0.zip](https://github.com/zero9178/C-Cpp-Coverage-for-CLion/files/3806148/C.C%2B%2B.Coverage-2019.2.0.zip) I have created a version of the plugin that should send you a notification of what the function is called right before the exception happens. Should help...

Something must have gone wrong when trying to find it. It will look in different places including the PATH however. Either way you can always change your settings by going...

I am not sure how to handle this as c++ is also a common name for GCC and people also still that on MacOS too. I could try doing --version...

What compiler are you using? Is the editor highlighted in any way (red or green)? If you are using AppleClang (which you might even if the executable is called g++)...

That assertion seems very concerning and might need some changes in either LLVM or the general approach of how the GC plugin works. The linker errors are probably due to...

I have posted https://reviews.llvm.org/D132708 to fix the first assert.

I've been thinking quite a bit about the testability of this PR and how to best review it once it's not WIP anymore and I got some questions and possible...

> I have posted https://reviews.llvm.org/D132708 to fix the first assert. This patch has landed in LLVM now and I have also bumped the version to build Pylir with (and that...