TryBugHunt
cppScope errorMedium

Unexpected segfault when accessing string data

BugFind the bug and fix the code

What it should do

Create a greeting message by appending a name to a base message. Example: createGreetingString("John") -> "Hello, John!"

What happens instead

Segmentation fault (core dumped)

const char* createGreetingString(const std::string& name) {
  std::string message = "Hello, " + name + "!";
  return message.c_str();
}

int main() {
  const char* greeting = createGreetingString("Alice");
  std::cout << greeting << 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 scope and closure bugs pattern

A variable shadowed in an inner block, or a reference to something that has gone out of scope.

What you'll practise

A medium C++ debugging exercise about scope and closure bugs: a variable shadowed in an inner block, or a reference to something that has gone out of scope.

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: The function createGreeting returns a pointer to a temporary std::string object's internal buffer, which becomes invalid once the function exits, leading to a dangling pointer.

The fix: Return a std::string object instead of a const char* pointer to ensure the string's lifetime extends beyond the function call.

Remember: Always be cautious when returning pointers to internal data of temporary objects in C++.

The pattern behind it: scope and closure bugs.

More scope and closure bugs 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/60026caa-75f6-496d-bcdf-d205f03b1d54" title="Debugging challenge: Unexpected segfault when accessing string data" 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/60026caa-75f6-496d-bcdf-d205f03b1d54">TryBugHunt</a></p>