Anonymous user
Stack traces: Difference between revisions
m
added whitespace before the TOC, added a Task (bold) header, added other whitespace to the task's preamble.
(Added Elixir) |
m (added whitespace before the TOC, added a Task (bold) header, added other whitespace to the task's preamble.) |
||
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.
This task calls for you to print out (in a manner considered suitable for the platform) the current call stack. The amount of information printed for each frame on the call stack is not constrained, but should include at least the name of the function or method at that level of the stack frame. You may explicitly add a call to produce the stack trace to the (example) code being instrumented for examination.▼
;Task:
The task should allow the program to continue after generating the stack trace. The task report here must include the trace from a sample program.▼
Print out (in a manner considered suitable for the platform) the current call stack.
▲
You may explicitly add a call to produce the stack trace to the (example) code being instrumented for examination.
▲The task should allow the program to continue after generating the stack trace.
The task report here must include the trace from a sample program.
<br><br>
=={{header|Ada}}==
| |||