TryBugHunt
cppLogic errorHard

Member initialization order mismatch with declaration

BugFind the bug and fix the code

What it should do

Initialize multiplier and base value in struct. Example: constructConfigPair(5) -> 10

What happens instead

Garbage value calculated because fields initialize in declaration order

#include <iostream>

struct ConfigPair {
    // Declaration order: factor is initialized before base!
    int factor;
    int base;

    ConfigPair(int b) : base(b), factor(base * 2) {}
};

int constructConfigPair(int b) {
    ConfigPair cp(b);
    return cp.factor;
}

int main() {
    std::cout << constructConfigPair(5) << std::endl;
    return 0;
}

Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).

⏱️0:00
Hints
🏆 0 hints = Flawless Solve
Think & Test Cooldown
2:00 remaining

Take a moment to read the bug symptom and trace the code with Run & Check before unlocking Hint 1.

Hint 2
Unlocks after Hint 1
Hint 3
Unlocks after Hint 2

This bug belongs to the logic errors pattern

The wrong operator, an inverted condition, a formula the right way round but backwards.

What you'll practise

A hard C++ debugging exercise about logic errors: the wrong operator, an inverted condition, a formula the right way round but backwards.

The checks your fix must pass

Signs of this kind of bug

Spoiler: why this bug happens(try it first; the hints get warmer one at a time)

What went wrong: In C++, class members are initialized strictly in the order they are declared in the class definition, regardless of the order in the constructor initializer list. factor was declared before base, so factor(base * 2) evaluated while base was still uninitialized garbage.

The fix: Reorder the member declarations so base is declared before factor.

Remember: Members are always initialized in declaration order. Always list constructor initializers in the same order as class member declarations.

The pattern behind it: logic errors.

More logic errors to practise

Embed this challenge on your site

Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.

<iframe src="https://trybughunt.com/embed/278e09e3-ab7e-4a90-857b-f06d2c79ea3b" title="Debugging challenge: Member initialization order mismatch with declaration" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/278e09e3-ab7e-4a90-857b-f06d2c79ea3b">TryBugHunt</a></p>