Call stack: Revision history

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

16 June 2024

24 May 2024

  • curprev 12:0812:08, 24 May 2024Helpful talk contribsm 673 bytes 0 Helpful moved page Call trace to Stack trace
  • curprev 12:0812:08, 24 May 2024Helpful talk contribs 673 bytes +673 Created page with "<!-- A stack trace is often printed to help give you an idea of what a process was doing, often as debug when something isn't quite right. Classical execution does function calls via the stack ('the stack' being a portion of memory a task reserves for this, and has a predictable structure -- a data stack), so the stack happens to be a great way to inspect what a process was executing at a point in time. The 'call stack' is basically what the stack shows about functi..."