为何LCOV忽略已执行代码行？代码覆盖统计异常问询

Great question! Let's break down why those lines aren't showing up in your LCOV report, even though you believe they're being executed:

1. Class Definition & Access Modifier Lines (Lines 6, 7, 10) #

LCOV tracks coverage based on executable machine code generated by the compiler—not every line of your source code. Lines like:

• class domath { (line 6)
• public: (line 7)
• }; (line 10)

are purely declarative code. They tell the compiler about the structure of your class, but don't translate to any actual machine instructions that run when your program executes. Since there's no code to execute here, LCOV has nothing to track, so it doesn't mark these lines as covered. This is totally expected behavior.

2. Object Instantiation Line (Line 13: domath math1;) #

Your domath class uses the compiler-generated default constructor (since you didn't define one yourself). Here's why this line isn't being counted:

• If you're using compiler optimizations (like -O1, -O2, or higher), the compiler will often optimize away this empty default constructor entirely. Since instantiating the object does nothing meaningful, there's no machine code generated for that line—so LCOV can't detect it as executed.
• Even without optimizations, the default constructor call might be inlined or merged into other code, making it impossible for LCOV to attribute execution to that specific line.

How to Get the Instantiation Line Counted (If You Need It) #

If you want line 13 to show up as covered, add an explicit empty constructor to your class. This forces the compiler to generate executable code for the constructor call:

class domath {
public:
    domath() {} // Explicit default constructor
    int multiply(int a, int b) {return a * b;}
};

Now when you instantiate domath math1;, the compiler will generate a call to this constructor, and LCOV will mark line 13 as executed. Note that this won't change anything for the class definition lines (6,7,10)—those still won't be counted, as they're still purely declarative.

A Quick Reality Check #

Don't stress too much about these missing lines! LCOV's purpose is to track code that actually does something—like your multiply function, test assertions, and core program logic. Declarative lines don't contribute to runtime behavior, so their absence from coverage stats doesn't mean your tests are ineffective.

内容的提问来源于stack exchange，提问作者Kevin4720