To start the Editor from the Debugger
When you start the Editor from the Debugger, MULTI creates temporary copies of source files so you can continue to debug your program while looking at the original source code. Changes that you make in the Editor affect the actual file, not the temporary file that the Debugger is using to show the original code. When you exit the Debugger, the temporary files are deleted.
To bring up the Editor on the Debugger's current source file, click the Edit button in the Debugger.
You can also start the Editor by entering commands in the Debugger Command Window. The following table summarizes which command to use to open a certain file:
Debugger commands that start the Editor
|
---|
To open
|
Enter
|
Examples and Comments
|
---|
The current source file
|
edit
|
n/a
|
A file by name
|
edit filename
|
n/a
|
A file by selecting it in a dialog box
|
editfile
|
n/a
|
A file that contains a certain procedure
|
edit procedure
|
If a procedure name is followed by a wildcard pattern, then a window appears with a list of procedures from which you select a procedure to edit. For example, the command edit f* opens a window that lists all procedures beginning with the letter f.
|
A file whose procedure has a certain breakpoint
|
edit numberb
|
For example, to edit the procedure containing breakpoint number three, use the command edit 3b. You can obtain breakpoint numbers with the B command.
|
A file whose procedure is at a certain stack depth
|
edit number_
|
For example, to edit the procedure at stack depth three, use the command edit 3_. You can obtain stack depths with the calls command.
|
Related topic:
Copyright © 1999, Green Hills Software. All rights
reserved.