backtrace
Error call history
A backtrace is a diagnostic report showing the sequence of function calls that led to a particular point in a program's execution, typically an error or crash.
Programmers use backtraces to debug code by tracing backward through the call stack to find where things went wrong: The backtrace showed the crash originated in the memory allocation routine.
Also called a stack trace.
Software error-locating tool
- breakpointCode execution pause marker
- exceptionDeviation from standard
- segfaultInvalid memory access error
- crashSudden violent impact
bug · fault · log · inspect · diagnose · analyze · dump · runtime
Active function chain
process · memory · address · pointer · heap · allocation · subroutine · invocation
A distinct event
- investigationFormal examination of facts
- analysisMethodical study of parts
- malwareHarmful computer programs
- cybersecurityProtection of digital systems
intrusion · rootkit · exploit · vulnerability · breach · reconstruction · audit · logging
debugger
Software error-locating tool
- breakpointCode execution pause marker
- exceptionDeviation from standard
- segfaultInvalid memory access error
crash · bug · fault · log · inspect · diagnose · analyze · dump · runtime · overflow
callstack
Active function chain
thread · process · memory · address · pointer · heap · allocation · subroutine · invocation · sequence
incident
A distinct event
- investigationFormal examination of facts
- analysisMethodical study of parts
- malwareHarmful computer programs
cybersecurity · intrusion · rootkit · exploit · vulnerability · breach · reconstruction · audit · logging · timeline