User Guide

Table Of Contents
432 Chapter 18: Debugging and Troubleshooting Applications
Exceptions
In the Administrator, when Exception Information is selected on the Debugging Settings page,
the debugging output includes a list of all ColdFusion exceptions raised in processing the
application page. This section looks like the following figure when displaying information about
an exception thrown by the
cfthrow tag using the dockable.cfm output format:
The exception information includes information about any application exceptions that are caught
and handled by your application code or by ColdFusion MX.
Exceptions represent events that disrupt the normal flow of an application. You should catch and,
whenever possible, recover from forseeable exceptions in your application, as described in
Chapter 14, “Handling Errors,” on page 307. However, you might also want to be alerted to
caught exceptions when you are debugging your application. For example, if a file is missing, your
application can catch the
cffile exception and use a backup or default file instead. If you enable
exception information in the debugging output, you can immediately see when this happens.
Trace points
In the Administrator, when Tracing Information is selected on the Debugging Settings page, the
debugging output includes the results of all
cftrace tags, including all tags that display their
results in-line. Therefore, the debugging output contains a historical record of all trace points
encountered in processing the request. This section looks like the following figure when you use
the classic.cfm output format:
For more information on using the
cftrace tag, see “Using the cftrace tag to trace execution
on page 436.