Stack traces: Difference between revisions
Content deleted Content added
Added Elixir |
m added whitespace before the TOC, added a Task (bold) header, added other whitespace to the task's preamble. |
||
Line 2: | Line 2: | ||
Many programming languages allow for introspection of the current call stack environment. This can be for a variety of purposes such as enforcing security checks, debugging, or for getting access to the stack frame of callers. |
Many programming languages allow for introspection of the current call stack environment. This can be for a variety of purposes such as enforcing security checks, debugging, or for getting access to the stack frame of callers. |
||
⚫ | |||
;Task: |
|||
⚫ | |||
Print out (in a manner considered suitable for the platform) the current call stack. |
|||
<br clear=all> |
|||
⚫ | |||
You may explicitly add a call to produce the stack trace to the (example) code being instrumented for examination. |
|||
⚫ | |||
The task report here must include the trace from a sample program. |
|||
<br><br> |
|||
=={{header|Ada}}== |
=={{header|Ada}}== |