Eclipse 3.4 / FD 2.01 expression error

[Matt Williams]

I got Eclipse 3.4 and FD 2.01 working, but I get the following error
when trying to highlight a variable, Right-click and choose Inspect
Expression:

An internal error occurred during: "has children update".
org.eclipse.debug.internal.core.WatchExpression cannot be cast to
org.eclipse.debug.core.model.IVariable

I also do not seem to be able to add Watch Expressions. I do not get
an error there, just nothing showing up in the Expressions panel.

I have not yet tried any troubleshooting such as uninstalling and re-installing.

--
Matt Williams
"It's the question that drives us."

[Darren Pywell [FusionDebug Team]]

Matt,

I'm getting this error sometimes too. It looks like something changed
in the 3.4 WatchExpressions.

We'll take a look and see what's happening.

Cheers,
Darren

[Peter Bailey [FusionDebug Team]]

Matt,

We have looked into this issue thoroughly, and now believe it to be an
Eclipse internal problem. The workings of the Inspect Expression view
requires this IVariable type casting for correct reading and output,
which is handled differently in 3.4 as Eclipse changed this to be more
efficient (it would seem). This is the same issue for the display of
the Watch Expressions, though they are being updated the UI is not
displaying them as this casting issue requires a subclass of IVariable
which is not used in this version. It would appear that this changed
late in development as we have had working versions of FD up until 3.4
M4 release at least.

We are not the only Eclipse debugger project to have suffered from
this.

This has been mentioned in more detail on the Eclipse site:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=238878 we have now
posted our findings also. As stated on the article, 3.5 would be the
expected fix, though we have requested any assistance possible to
correct this in the mean time. We are aware of the impact FD not
supporting 3.4 has, and as such we will continue to look for
workarounds and alternative fixes, though as you can appreciate we
cannot promise anything especially with these Eclipse internal
changes.

Thank you for your help,
Peter

On Jul 10, 12:24 am, "Matt Williams" <mgw...@gmail.com> wrote:

[Matt Williams]

Thanks for updating me. I'm sure it isn't easy to keep up with
projects such as Eclipse. I was also running 3.4 M4 prior to the final
release and did not have issues with that either. Let's hope the
Eclipse team hears enough squeaky wheels to release a patch.

Again, thanks for looking into it further and letting us know what you found.

Matt