Summary

This chapter explored the concepts that would not be required in the "perfect world"—troubleshooting, which is basically finding out why your application does not work as expected.

First, we described the available solutions for logging and tracing your Tcl application. From the log, logger ,or audit packages, you may chose the one that closest fulfils your expectations and requirements. We've shown how each of the packages work and what the key differences are between them.

Next, we described a variety of tools that allow you to take a good look at the internals, and analyse and interact with the running application. Starting from the TclDevKit Inspector, which is a tool that allows you to view the internal components of the application. It is a lightweight tool that can easily be used to connect to a running application, view or modify its parameters, and disconnect from it.

We then moved on to using a full-fledged TclDevKit Debugger with all its richness of features. We've shown...