TOC PREV NEXT INDEX

 


About TclPro Instrumentation


When you begin running an application, TclPro Debugger transparently processes the specified Tcl/Tk script. It modifies the code to enable communication between TclPro Debugger and the script. This process is known as instrumentation. TclPro Debugger launches the application with the instrumented script in place of the original script. Ajuba Solutions designed the instrumentation to be as unobtrusive as possible. However, you can expect some slowdown in applications as a result of the instrumentation.

You can specify which procedures to instrument in the Procedures window; see "Finding Procedures". You can also specify files and classes of procedures to leave uninstrumented; see "Changing Project Instrumentation Settings". In addition to the files and procedures that you tell TclPro Debugger not to instrument, there are also some instances of dynamically created code that TclPro Debugger cannot instrument. These include if statements with computed bodies and callbacks from Tcl commands. When the application is executing uninstrumented code, it cannot communicate with TclPro Debugger. If you want to interrupt or to add a breakpoint to the script while uninstrumented code is executing, the application cannot respond until it reaches the next instrumented statement.

TclPro Debugger indicates that a procedure or file is uninstrumented by listing the procedure or file name preceded by an asterisk ("*") in the Procedures window, Windows menu, and the Code display status bar.




http://www.ajubasolutions.com
Voice: (650) 210-0100
Fax: (650) 210-0101
support@ajubasolutions.com
TOC PREV NEXT INDEX