What is "stack-trace"

To stack trace is a report of the areas or frames active stack at a certain point in time while running a program and is often referred to as a stack trace^{(memory area)}.

A stack trace is commonly used during interactive debugging and post-mortem. Typically lists all functions that await return values in the stack at the time of the error. By examining what is in the stack and comparing it to what you expect, you can often determine how the error occurred. By inspecting the function containing the error, you may be able to edit and fix the problem.

A stack trace allows you to trace the sequence of nested functions called to the point where the stack trace is generated. In a scenario post-mortem works up to where the fault occurred (but not necessarily caused there). Side function calls are not visible on a stack trace.

Before you begin

Please navigate to the list of frequently asked questions to see if your question is similar to one that has already been answered.

The tag stack-trace should be used to mark issues related to generation, interpretation, debugging, or misunderstanding of cell crawls