🚀 go-pugleaf

Hi,

I recently upgraded from CW5.3 to CW6 running on a 500MHz Pismo PowerBook.

I'm developing a Java application. In CW5.3 I used the deprecated
MetroNub debugger primarily because the speed of the default
debugger (using the Sun Java Debugger API) was abysmal.

When I upgraded to CW6, I assumed that the same performance problems
would exists for the default debugger, and so I also installed the
deprecated MetroNub debugger again.

Unfortunately, the deprecated MetroNub debugger does not appear to
display the contents of objects correctly. Specifically, the name
of each variable is displayed as garbage, and I'm not convinced that
the contents are displayed correctly either. This all worked fine
on CW5.3.

I've tried the default debugger, but as expected, the performance 
makes it unusable (15 second for each step operation, 50 seconds
(or more) to update the display after a break point etc).

Is there anything I can do to either improve the performance of
the default debugger or make the deprecated MetroNub debugger
display object contents properly?

Help! Right now it looks as though I will have to downgrade back
to CW5.3...

--Nick