TryBugHunt
cppLogic errorMedium

Self-assignment in copy assignment operator

BugFind the bug and fix the code

What it should do

Assign buffer to itself safely and return stored value. Example: copyBufferValue(42) -> 42

What happens instead

Crash: double free or use-after-free when assigning object to itself

#include <iostream>

class SimpleBuffer {
public:
    int* ptr;
    SimpleBuffer(int v) : ptr(new int(v)) {}
    ~SimpleBuffer() { delete ptr; }
    
    SimpleBuffer& operator=(const SimpleBuffer& other) {
        // Missing self-assignment guard: this == &other deallocates own pointer!
        delete ptr;
        ptr = new int(*other.ptr);
        return *this;
    }
};

int copyBufferValue(int val) {
    SimpleBuffer b(val);
    b = b; // Self assignment deallocates ptr, then dereferences freed memory
    return *b.ptr;
}

int main() {
    std::cout << copyBufferValue(42) << 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 medium 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 operator=, deleting ptr before checking whether this == &other deallocates the memory of other.ptr when an object is assigned to itself, causing a use-after-free or crash.

The fix: Guard against self-assignment at the start of operator=: if (this == &other) return *this;.

Remember: Always protect copy assignment operators against self-assignment, or implement the copy-and-swap idiom.

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/9305cac4-b32a-4a67-b9b1-034c3fd29705" title="Debugging challenge: Self-assignment in copy assignment operator" 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/9305cac4-b32a-4a67-b9b1-034c3fd29705">TryBugHunt</a></p>