DTKDBG
Enable the UI Toolkit debugger
WSupported on Windows
|
USupported on Unix
|
VSupported on OpenVMS
|
|
The DTKDBG environment variable enables UI Toolkit debugging.
Value
Any value.
Discussion
If DTKDBG is set and Toolkit generates a fatal error, a window displays asking if you want to examine the window system. Answer y to start the Toolkit debugger. While a Toolkit program is running, you can enter debug mode by pressing Ctrl+R while performing any Toolkit input.
When DTKDBG is set, the debugger does the following:
- Checks for any %M_SIGNAL call that supersedes a pending menu entry and, if one is encountered, displays a message box indicating which menu entry the call is signaling and which entry is being superseded. At the prompt, select Yes to continue the operation. If you select No, the debugger calls U_ABORT, which generates a fatal Toolkit error.
- Displays a message box if a USTART_METHOD cannot be invoked, asking if you want to continue. If you select Yes, the program proceeds with non-DTKDBG behavior: it ignores the method. If you click No, the debugger calls U_ABORT, which generates a fatal Toolkit error.
Setting location
The environment. On Windows, this environment variable can also be set in the [synergy], [dbr], or [myprog] section of synergy.ini (where myprog is any .dbr file).
Used by
UI Toolkit
See also
- WINDBG command for information on invoking the UI Toolkit debugger from the Synergy debugger prompt
- U_DEBUG routine for instructions on invoking the Toolkit debugger programmatically
- DTK_BOUNDS environment variable to enable bounds checking in UI Toolkit
Examples
On Windows,
set DTKDBG=1