To open the debugger, select Start debugger . If you have a script paused in the main window, the debugger opens at the current position of the test. If you do not have a paused script, the debugger automatically begins running the main file and positions the cursor at the start of the script. or clickThe debugger consists of a call stack area, action buttons, and the debugger command line interface (CLI) window, as shown in Figure 1. The debugger is positioned between the Abaqus PDE main window and the message area. Figure 1. The
Abaqus
PDE debugger.
The debugger uses a custom Python module named atxPdb, based on the Python pdb module. You can enter Pdb commands in the debugger CLI; you can also enter any Python statements in the debugger CLI. Python statements are executed in the same process—GUI, kernel, or local—that is running the current script (for more information, see Running a script). Note: If you enter a command in the debugger CLI and it does not seem to work, it may be conflicting with a Pdb command. The call stack area shows the commands that are currently being executed.The debugger contains a tool to watch variables as scripts are executed. To add a variable to the watch list, click mouse button 3 over the variable name in the Abaqus PDE main window and select Add Watch: variable name from the menu that appears. The Abaqus PDE adds the variable to the watch list, indicating the namespace that the variable is defined within, the variable name, the type of data the variable can store, the current value, and the file and line where the variable is located. When you execute or step through the script, the variable information is updated as needed. You can also activate the watch list tool after starting the debugger by selecting from the action buttons below the call stack area or by selecting . Abaqus displays the Watch List area below the debugger or below the main window if the debugger is not open. You can also customize the following aspects of variable display in the Watch List:
|