TryBugHunt
goNull / UndefinedMedium

Price lookup crashes for an item the shop does not sell

BugFind the bug and fix the code

What it should do

priceWithTax(name) looks up a product and returns its price in cents plus 10% tax, or the error "unknown product: <name>". priceWithTax("pen") returns 165.

What happens instead

priceWithTax("stapler") crashes with panic: runtime error: invalid memory address or nil pointer dereference.

package main

type product struct {
    name  string
    cents int
}

var catalog = []product{{"pen", 150}, {"notebook", 400}, {"bag", 2500}}

func findProduct(name string) *product {
    for i := range catalog {
        if catalog[i].name == name {
            return &catalog[i]
        }
    }
    return nil
}

func priceWithTax(name string) (int, error) {
    p := findProduct(name)
    return p.cents * 110 / 100, nil
}

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 null and undefined errors pattern

A nil pointer or nil map that the code uses as if it held a value.

What you'll practise

A medium Go debugging exercise about null and undefined errors: a nil pointer or nil map that the code uses as if it held a value.

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)

findProduct uses nil to mean "no such product", which is a normal Go pattern, but the caller never checks for it and reads p.cents straight away. Dereferencing a nil pointer panics. The function already returns an error, so the fix is to turn the nil into that error. Whenever a function can return nil, the caller has to handle it on the very next line; returning (value, error) or (value, ok) from the lookup itself makes that harder to forget.

The pattern behind it: null and undefined errors.

More null and undefined errors to practise

Related errors

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/393dfcc1-70f9-4e8a-83f0-52cbda1511f8" title="Debugging challenge: Price lookup crashes for an item the shop does not sell" 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/393dfcc1-70f9-4e8a-83f0-52cbda1511f8">TryBugHunt</a></p>