Hi Richard,
Breakpoints in Eclipse are actually associated to plugins (like
FusionDebug). When you set a breakpoint then the breakpoint is created
along with the id of the plugin that created it. In the case of a
FusionDebug plugin we record some extra information (such as the
source code path) on the breakpoint that we can use during debugging.
It's possible however to create a breakpoint inside your CFML code
which is associated to a plugin other than FD. This tends to happen
because Eclipse can only associate one plugin to a command (Toggle
Line Breakpoint) that a key stroke (e.g. CTRL-SHIFT-B) represents.
This means that when multiple plugins register themselves for a given
keystroke Eclipse tends to pick the last plugin installed that is
associated to a given keystroke and file extension as the one that
will be used to create the breakpoint.
FusionDebug is very clever here and although the breakpoint isn't
associated to it, it still honors the breakpoint if it is connected
and debugging. This means that the breakpoint still fires but we don't
get to output the extra information.
There are a couple of things you can do about this:
1. On the right mouse click menu in the editor we've added a Menu item
called Toggle Line Breakpoint with a little red bug by the side of it.
This menu item always creates an FD breakpoint
2. You can find the other plugin that is "stealing" the breakpoints
from FD and uninstall it if you don't use it
Hope that helps,
Darren