We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
I have some strange Light Coverage result reported by AQTime (8.71.3483.7)
It shows thats the lines containing only brackets (from if-else or try-catch blocks) and `if-else` keywords are uncovered.
An exmaple code:
template<typename T>
class Klass
{
public:
void do()
{
try
{
if ( ... )
{
//...
}
else /* this line is reported as uncovered */
{
//...
} /* this line is reported as uncovered */
}
catch (SomeEx&)
{
//...
} /* this line is reported as uncovered */
catch (SomeOtherEx&)
{
//...
} /* this line is reported as uncovered */
}
};
The whole code is actually covered but the report shows such lines uncovered.
is it expected behavour?
How can I get rid of it?
thanks
thanks AlexKaras, it was a good hint.
Indeed, I did run Coverage Profiler with none-Release configuration in MSVC.
Without /O options MSVC would generate unreachable jmp instructions for such `else` or `bracket` lines.
It is not wrong but just not nice with MSVC for none-optimzed code generation. https://godbolt.org/z/qdE0ke and https://godbolt.org/z/9Z0Pft
I assume that AQTime profiler just traces if generated instructions are executed or not. That is why I get this strange result.
Hi,
If all other lines from your example are reported as covered, then I would recommend to address Support directly via the https://support.smartbear.com/message/?prod=AQtime form and let guys know what development environment was used to create your profiled application.
Also I would recommend to double check if all compilation requirements have been met - https://support.smartbear.com/aqtime/docs/profiling-with/prepare-apps/index.html
thanks AlexKaras, it was a good hint.
Indeed, I did run Coverage Profiler with none-Release configuration in MSVC.
Without /O options MSVC would generate unreachable jmp instructions for such `else` or `bracket` lines.
It is not wrong but just not nice with MSVC for none-optimzed code generation. https://godbolt.org/z/qdE0ke and https://godbolt.org/z/9Z0Pft
I assume that AQTime profiler just traces if generated instructions are executed or not. That is why I get this strange result.