Author:halw

Date:2009-01-14T18:16:46.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@163 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-01-14 18:16:46 +00:00
parent 7c808cf461
commit 3d675b2956
8 changed files with 26 additions and 18 deletions

View File

@@ -3,6 +3,7 @@
[[Property:uuid|ff70f68f-31db-c5d1-4d68-7b0fc70b1dd7]]
[[Image:call-stack-tool]]
The call stack tool gives information about the current call stack of a debugged application.
It is mainly composed of a list representing the call stack elements, where the entry feature of the program is at the bottom and the top of the call stack is at the top. <br/>
@@ -14,10 +15,14 @@ It is mainly composed of a list representing the call stack elements, where the
On top of this list, a line gives the state of the debugged application, and another one describes the exception that caused the application to stop, if any. For more information concerning exceptions, see the [[Supported exceptions|supported exceptions]] .
The button [[Image:debug-exception-dialog-icon]] is used to open the Exception dialog which show the exception details. For instance a call on Void target in a dotnet system would popup :
<center> [[Image:exception-dialog]] </center>
[[Image:exception-dialog]]
When more than one thread is available to the debugger, you can switch from one to the other, for that you have to click on the thread's id "0x000..." and select from the popup list of available threads. Or (recommended) you can use the [[Threads tool|threads tool]] (clicking on '''Show threads panel''' will show the threads tool).
<center> [[Image:call-stack-tool-with-threads]] </center>
[[Image:call-stack-tool-with-threads]]
In the toolbar, the button [[Image:general-save-icon]] gives the possibility to [[Save call stack|save the call stack]] to a text file, and the button [[Image:general-copy-icon]] copy to the clipboard. The [[Image:debugger-callstack-depth-icon]] button makes it possible to choose which call stack depth should be displayed in the list (the default is to display the 100 top stack elements, but it is configurable with the same button).

View File

@@ -1,12 +1,14 @@
[[Property:title|Call stack tool]]
[[Property:weight|-13]]
[[Property:uuid|8c3cd0fe-78aa-7ec6-f36a-2233a4e26755]]
* [[Callstack tool: Introduction|Introduction]]
* [[Call stack tool: Interface|Call stack tool]]
* [[Information relative to a stack element|Information about the current stack level]]
* [[Supported exceptions|Supported exceptions]]
* [[Save call stack|Save call stack command]]
The call stack is the list of routines that have been entered during execution, but not yet exited since execution started. The list can be considered a '''stack''' structure, because before any routine, say <code>my_routine</code>, can exit, any routine that <code>my_routine</code> may have called must have exited first. Therefore the last entered feature is listed at the top of the stack and the program root feature is its bottom.
There is one level in the call stack, the currently selected element, that has a special status. It is the level to which all debugging tools refer. The currently selected element is, as you might guess, user-selectable. So it is possible to move along the call stack, changing the currently selected element, and view information in the debugging tools about any level..
To keep a record of a call stack (for example in order to indicate to other people where a problem occurred), you can [[Save call stack|save the call stack]] to a text file.
Information concerning the call stack is spread over several graphical components:
* The entire call stack, depicted as a list of elements, is displayed in the [[Call stack tool: Interface|call stack tool]] .
* [[Information relative to a stack element|Information concerning the current call stack element]] is displayed in the feature tab, the locals view, and is used to provide the expressions evaluations contained in the [[Evaluation tool or Watch tool|Expression evaluator tool]] .