jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 100 Many additional features are planned for the debugger. See Future Plans (future/missing features) for details. 19.1 Debug Window • Toolbar • Threads Window • Call Stack Window • Variables Window • Breakpoints • Watches 19.2 Toolbar Step Over - steps the selected thread within the current method or code block. The thread must be suspended to step. In normal step mode, this will execute approximately one line of source code in the current method. If "byte code size steps" is selected, approximately one byte code instruction will be executed. While the thread is stepping, "(stepping)" is displayed in its description in the threads window. Multiple threads can be stepped at the same time. Hitting "Suspend" will kill the step. When the step is completed, if the stepping thread or no thread is selected, the current source line will be selected; if another thread is selected, no action will be taken. Step In - like step over, but will enter any method calls. Step Out - like step over, but will step out of the current method or code block. Step to Cursor - runs to the cursor for the active CSD window within the virtual desktop. All breakpoints are ignored during this operation, but watchpoints are not. Suspend - suspends the selected thread, or all threads within the selected group. Resume - start the selected thread, or all threads within the selected group. Byte Code Steps - when on, use the smallest step size possible Otherwise, the step size is approximately one source line. Suspend New Threads - if on, any new threads that start will immediately be suspended. If on when the debugging process is started, all startup threads are suspended as soon as is possible. 19.3 Threads Window Shows the state of each thread, organized within the thread group tree. Suspended threads are shown in red, running threads in green. This window in updated dynamically, so you can see the state of running threads change. The thread description is as follows: name [state] (debugger action/state) monitors name - name given to the thread. You should name any threads you start, to make them easier to track. - shows jGRASP's current suspend count for the thread (x), and the actual count.(y). This is for our debugging purposes only, it should not be of interest to the user unless jGRASP is not working correctly. The actual suspend count may be one higher than jGRASP's suspend count temporarily, but they should be the same most of time. jGRASP's suspend count should always be 0 or 1.
DRAFT, February 18, 2003, Page 101 [state] - shows the current suspend state: running, waiting, waiting on monitor, sleeping, not started, zombie, or unknown. (debugger action/state) - shows what the debugger is currently doing with respect to the thread: at breakpoint, suspended, running to cursor, or stepping. If none of these are true (the thread is running normally), nothing is shown. monitors - shows the monitors owned by the thread, by id number. This is the same id number shown for objects in the variables window. If the thread is waiting on a monitor, this monitor is shown in [braces]. For a simple, non-gui application, there will be your "main" thread, any threads that your code creates, and several system support threads (Signal Dispatcher, Reference Handler, Finalizer). For applets or gui applications, there will be numerous event queue, gui, and system threads. 19.4 Call Stack Window Shows the current call stack for the selected thread, if the thread is suspended. When the thread is resumed, this window is disabled. Each frame of the stack shows the method, filename and line number if available, and program counter. The program counter is the current byte code index within the method. Selecting a frame will select the source line, if the corresponding file can be found, and show the associated variables in the variables window. Source files are located using the "Sources" entry of the global settings. 19.5 Variables Window Shows the available variables for the current frame of the call stack. Composite objects can be expanded to see the fields or array elements. The target code must be compiled in debug mode, or not much information will be available here. this or static - shows fields for the current object if within an instance method or code block, or static fields available within the current static context. Arguments - shows arguments to the current method if within a method. Locals - shows the current local variables. Objects are shown as squares, primitive types as triangles. All non-fields are colored blue. Field icons are color coded based on the declared type of the object containing them (the actual type may be a subclass or interface implementation). The coding is: orange - field is declared in a superclass of the declared type of the containing object or an interface implemented by a superclass. green - field is declared in the declared type of the containing object. cyan - field is declared in an interface implemented by the declared type of the containing object. yellow - field is declared in a subclass of the declared type of the containing object or an interface implemented by a subclass. Static fields are shown in italic type. When a field is selected, the type in which it was declared is shown at the bottom of the variables window. For arrays, at most ten elements are shown at once. To change the elements that are shown, select the object then click on it (but don't double click). A slider bar will appear, on which you can select the first element shown. Any masked fields are shown with a grey bar over the icon.
Page 1 and 2:
The Table of Contents Index Handboo
Page 3 and 4:
DRAFT, February 18, 2003, Page ii 4
Page 5 and 6:
DRAFT, February 18, 2003, Page iv 1
Page 7 and 8:
DRAFT, February 18, 2003, Page vi 2
Page 9 and 10:
Overview of jGRASP DRAFT, February
Page 11 and 12:
DRAFT, February 18, 2003, Page 3 sp
Page 13 and 14:
DRAFT, February 18, 2003, Page 5 Pr
Page 15 and 16:
DRAFT, February 18, 2003, Page 7 Co
Page 17 and 18:
11 Control Structure Diagram (CSD)
Page 19 and 20:
1 Installing jGRASP DRAFT, February
Page 21 and 22:
2.1 Creating a New File DRAFT, Febr
Page 23 and 24:
In the upper right corner of the CS
Page 25 and 26:
2.2 Saving a File DRAFT, February 1
Page 27 and 28:
2.4 Loading a File DRAFT, February
Page 29 and 30:
DRAFT, February 18, 2003, Page 21 4
Page 31 and 32:
DRAFT, February 18, 2003, Page 23 O
Page 33 and 34:
2.7 Line Numbers DRAFT, February 18
Page 35 and 36:
DRAFT, February 18, 2003, Page 27 T
Page 37 and 38:
2.9 Running a Program DRAFT, Februa
Page 39 and 40:
3 The Control Structure Diagram (CS
Page 41 and 42:
DRAFT, February 18, 2003, Page 33 n
Page 43 and 44:
Selection (cont’d) switch (when b
Page 45 and 46:
3.4 CSD Templates DRAFT, February 1
Page 47 and 48:
3.6 Reading Source Code with the CS
Page 49 and 50:
Consider the fragment at right with
Page 51 and 52:
4 Projects DRAFT, February 18, 2003
Page 53 and 54:
4.2 Adding files to the Project DRA
Page 55 and 56:
4.4 Generating Documentation for th
Page 57 and 58: 4.5 Jar file Creation and Extractio
Page 59 and 60: DRAFT, February 18, 2003, Page 51 I
Page 61 and 62: DRAFT, February 18, 2003, Page 53 j
Page 63 and 64: DRAFT, February 18, 2003, Page 55 M
Page 65 and 66: DRAFT, February 18, 2003, Page 57 a
Page 67 and 68: 5.5 Displaying Dependencies Between
Page 69 and 70: 5.8 Saving the UML Layout DRAFT, Fe
Page 71 and 72: DRAFT, February 18, 2003, Page 63 b
Page 73 and 74: DRAFT, February 18, 2003, Page 65 t
Page 75 and 76: DRAFT, February 18, 2003, Page 67 V
Page 77 and 78: DRAFT, February 18, 2003, Page 69 T
Page 79 and 80: Part 2 - Reference DRAFT, February
Page 81 and 82: DRAFT, February 18, 2003, Page 73 i
Page 83 and 84: 9.4 Requirements for the Integrated
Page 85 and 86: 13 Known Bugs DRAFT, February 18, 2
Page 87 and 88: Unicode support - this will require
Page 89 and 90: Section 3. Disclaimer of Warranty D
Page 91 and 92: * . * DRAFT, February 18, 2003, Pag
Page 93 and 94: DRAFT, February 18, 2003, Page 85 A
Page 95 and 96: DRAFT, February 18, 2003, Page 87 S
Page 97 and 98: 17.13 Projects DRAFT, February 18,
Page 99 and 100: 17.18 Jar/Zip Extractor Dialog DRAF
Page 101 and 102: DRAFT, February 18, 2003, Page 93 e
Page 103 and 104: 18.8 Find Dialog / Page DRAFT, Febr
Page 105 and 106: DRAFT, February 18, 2003, Page 97 s
Page 107: \xnn hexadecimal representation of
Page 111 and 112: DRAFT, February 18, 2003, Page 103
Page 113 and 114: 22.5 View Menu DRAFT, February 18,
Page 115 and 116: • CSD Page • Colors Page • Fo
Page 119 and 120: 23.2.1.11 View Page DRAFT, February
Page 123 and 124: 23.4.3 UML Print Settings Page Marg
Page 125 and 126: File syncing may cause jGRASP to lo
Page 129 and 130: flags..............................
show all

jgrasp handbook

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?