Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the null and undefined errors pattern
Cannot read properties of undefined, NoneType has no attribute, NaN appearing from nowhere.
What went wrong: Declaring a map variable with var initializes it to nil. In Go, reading from a nil map is safe and returns the zero value, but writing or assigning to a nil map triggers a fatal runtime panic.
The fix: Initialize the map before assignment using make(map[string]string) or a map literal map[string]string{}.
Remember: Always allocate memory for maps with make() before inserting key-value pairs.
The pattern behind it: null and undefined errors.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/9792dd68-e021-4d91-9537-0c94ed1f428e" title="Debugging challenge: Panic on assignment to uninitialized nil map" 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/9792dd68-e021-4d91-9537-0c94ed1f428e">TryBugHunt</a></p>