In This Book

Using Startup Command Files

When you invoke the debugger, it executes three startup command ￿les. Startup command ￿les contain commands that de￿ne command aliases and commands that customize the debugging environment.

The startup ￿les and their order of execution are:

1.User interface manager startup ￿le. Contains default de￿nitions for macros and for debugging environment settings. You can override these defaults de￿nitions using your personal startup ￿le (see \Using a Personal Startup File to Customize the Debugger") . To ￿nd out the name and location of the user interface startup ￿le for each user interface manager, see Appendix E.

Note

If you specify -doon the dde command line, the debugger

 

executes the -dooption's command list after executing the user

 

interface manager startup ￿le.

 

 

2. Personal startup ￿le. Contains commands that tailor the debugging

 

environment to your personal tastes and that de￿ne personal command

6

aliases. \Using a Personal Startup File to Customize the Debugger"

 

describes personal startup ￿les and how to create them.

 

3.Target manager startup ￿le. Contains macro de￿nitions speci￿c to the target machine. For example, it contains a de￿nition of the macro regs, which displays the machine registers.

The debugger executes the target manager startup ￿le after invoking or attaching to a target program, but before activating the target program. The debugger re-executes the target manager startup ￿le whenever you issue the debug command. See Appendix C for more information on the target managers.

Customizing the Debugger 6-3