Debugging Tools for Windows |
The Settings section enables you to define the primary settings for ADPlus. Most of these settings are equivalent to command-line parameters.
You can include as many instances as you want for the ProcessID, ProcessName, Spawn. and Notify elements.
<AttachInterval> inseconds </AttachInterval>
<AttachRepeats> numberofrepeatedattachments </AttachRepeats>
<RunMode> runmode </RunMode>
<LastScriptCommand> LastCommand </LastScriptCommand>
<Option> IIS </Option>
<Option> Quiet </Option>
<Option> NoTlist </Option>
<Option> NoTsCheck </Option>
<Option> NoFreeSpaceChecking </Option>
<OutputDir> OutputDirectoryName </OutputDir>
<ProcessID> PID </ProcessID>
<ProcessName> ProcessName </ProcessName>
<GenerateScript> ScriptName </GenerateScript>
<Spawn> Spawn Command </Spawn>
<Sympath> Symbol Path </Sympath>
<SympathPlus> Symbol Path to add </SympathPlus>
<Notify> { ComputerName | UserName } </Notify>
<Debugger> Debugger </ Debugger >
</Settings>
The Settings section contains the following elements:
Void indicates that no debugger command is added. In this situation, you must manually enter the last command in the debug session.
The default behavior is Q. Setting LastCommand to something other than the default is required only if you will use the CTL+C behavior (bpe exception) to induce dumps.
For more information about the corresponding command-line switches, see ADPlus Command-Line Options.