When a program crashes, it can leave a trail showing exactly how it got there. That trail is the stack trace.
Fresh snow, a toppled flower pot and a trail of footprints leading right to it. Follow the prints backwards and you know exactly which way the culprit came.
A stack trace is that trail for a crash. It’s a list the program produces showing the chain of steps that led to the exact line where it failed.
What it looks like
A block of lines, often scary-looking, something like:
- the error at the top: what went wrong
- then each step that led there: which file, which line
- back to where it all started
Why “stack”?
Programs work by one task calling another, which calls another, like a stack of plates. When something fails, the trace lists every plate in the stack at that moment.
What it isn’t
It isn’t meant for customers. It’s a clue for developers. A good app shows you a friendly error message and saves the stack trace in its log.
Where the comparison breaks down
Footprints can be faked or smudged. A stack trace is exact: it shows the real path, step by step.
How the words fit together
A bug causes a crash. The stack trace shows where. It’s saved in the log and used for debugging.
Reporting a crash? Copy the whole stack trace, not just the last line. The useful clue is often in the middle.

When you'll hear it
“Send me the stack trace.” Copy the crash details so I can see where the code failed.
“It's buried deep in the stack.” The problem is several steps into the chain, not at the top.
“The trace points to a library.” The crash happened inside someone else's ready-made code we use.
“When the app crashes for a customer, do we capture the details automatically?”


