[FDS-96] FusionDebug 2.0.1 Release Notes and Resolved Issues

FusionDebug Rev. 2.0.1

RELEASE NOTES KNOWN ISSUES

Status: May 25th, 2007

RELEASE NOTES

FusionDebug Rev. 2.0.1

We appreciate your feedback. Please use the web form or send mail to:

FusionDebug client has been tested using Eclipse Platform 3.1 and 3.2 on Microsoft Windows XP SP2
and on GNU/Linux Fedora Core 5 (kernel 2.6.17s-smp) under Gnome. FusionDebug is a pure Java
application with no native dependencies, and so runs on all OS platforms for which Eclipse is
available.

We recommend installing the Eclipse SDK package. This can be obtained from:

http://www.eclipse.org/downloads/

We recommend also installing the CFEclipse package, which provides a capable environment for
working with CF scripts within Eclipse. This can be obtained from:

http://www.cfeclipse.org/

KNOWN ISSUES

Many of these issues can be resolved by disconnecting FusionDebug (by selecting the blue
“FusionDebug” line in the Debug view, and clicking the red Disconnect icon).

JDWP Connections Prevent JRUN Container Restart

When the JDWP connection begins a variable fetch or evaluation, this can in some cases cause
the JDWP debug agent to prevent JRun’s service controller (used by Windows Services) from
restarting the container. In this case, disconnecting FusionDebug usually solves the issue.

Some Numerical / Complex CF Types Decode to Java Types, Not CF Types

We’re working hard on being able to decode all CF complex types. Most types are already
implemented – structs, arrays, XML objects, CFCs, Functions etc. In some cases, you might see
an undecoded type in the Variables and Expressions view (“… instance of …”) or a plain
string representation of the object.

Step Over sometimes requires > 1 keypress to advance the cursor.

This is because some lines of CF code perform multiple actions and require you to press
step for each action that they perform.

Step Into CFC’s is sometimes requires > 1 keypress to step into the CFC.

With the current instruction pointer located on the CFINVOKE tag, keep clicking Step Into until
the CFC is loaded. The parameters and other initialization actions are performed before the CFC
is called. You may have to push step into until this initialization is complete.

*Step Requests sometimes jump around to lines of code that are not sensible. *

This is a limitation of how CF processes and optimizes pages at compile time.

Some CFM/CFC files are listed multiple times with different line numbers in the stack although they are only called once

This is the result of compile time optimization of the CF code by the compiler. You can
workaround this issue by recompiling the affected page while FusionDebug is attached.
FusionDebug will ask the compiler to not optimize the code in this way and produce files that
are friendly to debugging. You must have the Compile CF pages in debug friendly mode checked
on in the launch configuration for this feature to work.

Sometimes variables or scopes are not shown/empty (ObjectCollected exception)

This is usually due to the way Java handles memory allocations for debuggers. Performing a
step usually corrects this.

Calling CF functions which are reentrant to the currently halted thread may cause the VM to hang

You cannot set/clear breakpoints with CTRL-SHIFT-B when in the CFEclipse perspective

CFEclipse does not support the CTRL-SHIFT-B keystroke when in the CFEclipse perspective. You
can toggle the breakpoint by right mouse clicking on the line you wish to set the breakpoint
on and using the Toggle Line Breakpoint menu item.

*Sometimes breakpoints don’t fire. *

In the Debug configuration, make sure the Target System Type is set correctly: checked for
Windows, unchecked for Unix.

*Breakpoints set on a blank lines may not always fire. *

Since FD 2.0.1 breakpoints can be set on blank lines. FD cannot always get breakpoints to
fire on blank lines because they are sometimes optimized away by the CF compiler.

Breakpoints on <cfreturn> statements should now fire (from FD 2.0.1)

Eclipse Outputs Text To The Console

If you start Eclipse Workbench from a Unix terminal session, you may see occasional
debugging output to the system STDOUT (System.out) and STDERR (System.err) streams.

Wrong File Selected

When a breakpoint or step event fires, FusionDebug does its best to find the source file. If the
same file exists multiple times in different projects, the wrong one may be selected
Use the source code lookup tab on the Launch Control to correct the source code lookups.

While debugging the page simply terminates

Check in the CF Administrator if you have Timeout Requests after ( seconds ) activated
When checked, requests that take longer than the specified time are terminated. This normally
prevents unusually long requests from occupying server resources and impairing the performance
of other requests. This feature will however also terminate pages that you are debugging if you
exceed the time limit. Deactivate this feature while debugging.

If your system is monitored by FusionReactor with crash protection activated, FusionReactor may
terminate the page if it exceeds the Request Timeout limit that has been configured. Please
deactivate crash protection in FusionReactor.

RESOLVED ISSUES