Paul,
Thanks for your reply. I have tried to get JDEbug to
run, with disappointing results. It will sometimes (I haven't
psyched out the magic) run an app; but never stops at
breakpoints, refuses sometimes to display the CLI buffer,
and generally acts squirrely.
Ken
On 7-Dec-00 at 09:22, Paul Kinnucan ([EMAIL PROTECTED]) wrote:
> At 08:56 AM 12/7/00 -0500, Ken Ketchum wrote:
> >Hello all,
> >
> >This from the Sun docs
> >indicates to me that JDEbug will just not work on Solaris with
> >j2sdk v1.3, since there is no classic VM.
> >
> >Is there any way to get JDEbug running under Solaris with this latest
> >Java SDK?
> >
> >My environment:
> >Solaris 2.6 SPARC
> >jde 2.2.5
> >speedbar 0.12
> >semantic 1.2.1
> >J2SE 1.3
> >Xemacs 21.1
> >
> >
> >Thanks for any help.
> >
>
> It's possible that the problems with debugging in Hotspot mode were
> confined to the Windows platform or have been fixed for the Solaris
> release.
>
> I think it's worth trying JDEbug on Solaris JDK1.3 to see if it works.
>
> I am copying this message to the Sun debug team in hopes that they can
> supply a more definitive answer to your question.
>
> - Paul
>
>
> >Ken Ketchum
> >
> >
> > from
> >http://java.sun.com/j2se/1.3/docs/tooldocs/tools-changes.html
> >
> >
> >Version 1.3 of the Java 2 SDK contains the new Java 2 Client Virtual
> >Machine with Java HotSpotTM technology as the default virtual machine for
> >running applications and applets. The virtual machine implementation from
> >previous versions of the SDK (the Classic VM) is still included with
> >the Java 2 SDK for Win32 platforms. It is not included with
> >the Java 2 Runtime Environment nor with the Java 2 SDK for the
> >Solaris operating environment. On the Win32 SDK, the classic VM
> >can be invoked by using the -classic option when launching
> >applications.........
> >
> >
> >
>
>
