call
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | call [2006/07/25 21:22] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======Synopsis: | ||
| + | [[call]] | ||
| + | |||
| + | ======Description: | ||
| + | [[CALL]] produces a gdb/ | ||
| + | executed. | ||
| + | tracing back from the current command, to the command that called it, | ||
| + | and so forth until the [[CALL]] command itself it listed. | ||
| + | alias might have the following alias stack: | ||
| + | |||
| + | [ 0] call | ||
| + | [ 1] go | ||
| + | [ 2] get_set | ||
| + | [ 3] get_ready | ||
| + | [ 4] on_your_marks | ||
| + | [ 5] /superalias | ||
| + | |||
| + | In this example, [[CALL]] was run from the " | ||
| + | called from " | ||
| + | the way down to the original command executed. | ||
| + | |||
| + | Command names appear precisely as they are typed in (which means, if | ||
| + | an alias is called with a / in front of it, the slash will appear in | ||
| + | the stack listing). | ||
| + | were to crash, [[CALL]] is executed before the client terminates, to aid | ||
| + | in debugging. | ||
| + | |||
| + | ======History====== | ||
| + | [[CALL]] first appeared in EPIC3.001. | ||
| + | |||
| + | #$EPIC: call.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ | ||
| + | |||
call.txt · Last modified: 2006/07/25 21:22 by 127.0.0.1
