Hi Ralph,
Some things you should be aware of concering debugging with JDK 1.3:
(1) JDK 1.3 includes a new version of jdb based on JPDA whose interface
differs from the old jdb. JDK 1.3 also includes the old version of jdb,
named, oddly enough, oldjdb. The JDE's jdb interface cannot parse the
output of the new jdb. That is why the JDE appears to hang when you try to
debug with jdb. The workaround is to use JDEbug or oldjdb for debugging
applications. You can use JDEbug to debug applets by running the applet as
an application.
(2) The JDE's applet debug command invokes appletviewer with the -debug
option. I believe that the appletviewer in turn invokes jdb on the applet.
The end result is that the JDE hangs for the reason stated in item 1. A
workaround might be to rename oldjdb to jdb.
(3) JDK 1.3 delivers two different vm's: a JRE vm and a development vm. The
JRE vm runs only in hotspot mode. The development vm runs in hotspot mode
(by default) or classic mode (if you specify the -classic) option. If you
try to run the JRE vm in -classic mode, you get an error.
(4) I need to update the JDE to support the new version of jdb. I will do
this as soon as possible.
- Paul
At 03:22 PM 6/15/00 +0100, you wrote:
>Hi,
>I set the Jde Applerviewer Option VM Args to the following :
>
>/----------
>Jde Appletviewer Option Vm Args: [Hide]
>[INS] [DEL] Argument: classic
>[INS]
> [State]: you have set this option, but not saved it for future
>sessions.
>Specify arguments (e.g., -Xmx16m) to the vm that runs appletviewer.
>[More]
>/-----------
>
>and now I get the following error message :
>
>/-----------
>cd d:/RJocham/CodeExamples/javabeansexamples/chapter8/
>appletviewer -Jclassic -debug Applet.html
>
>java.lang.NoClassDefFoundError: classic
>Exception in thread "main"
>Debugger exited abnormally with code 1
>/------------
>
>My O'Reilly 'Java in a Nutshell V1.3' tells me the following :
>
>page 209 : Client or Classic VM
>[...] The Client VM uses Sun's HotSpot [...] this is the default VM.
>To select the 'Classic VM', specify the -classic option.
>
>page 201 : appletviewer
>-J<javaoption>
>This option passes the specified <javaoption> as a command line
>argument to the Java interpreter. [...]
>
>appletviewer also recognizes the -class, -native and -green options
>that the Java interpreter recognizes. [...]
>
>So I had a play on DOS :
>
>1.
>appletviewer -classic Applet.html // works fine -> applet starts
>
>2.
>appletviewer -Jclassic Applet.html // shows the following error :
>
>Exception in thread "main" java.lang.NoClassDefFoundError:
>
>We know this error message from the error message above!
>
>As the 'J' is being added by JDE, I dare to say that there is a
>problem, either the applerviewer or the JDE don't do their job.
>
>Any suggestions or better advice ?!?!
>
>Thanks
>Ralph
>
>
>
>"Ensinger, Karsten" wrote:
>>
>> Hi Ralph!
>>
>> Following the mailing list it is not possible to use JDEbug for debugging
>> an application which is started within a HotSpot VM.
>> You have to start the VM via "-classic".
>>
>> Regards
>> Karsten Ensinger
>> Dresdner Kleinwort Benson
>> Global Markets Information Technology
>> - Business Analysis Fixed Income -
>> Phone +(49) 69 263-12338
>> Fax +(49) 69 263-10294
>> Mail [EMAIL PROTECTED]
>>
>> > -----Original Message-----
>> > From: Ralph Jocham [SMTP:[EMAIL PROTECTED]]
>> > Sent: Thursday, June 15, 2000 13:10
>> > To: [EMAIL PROTECTED]
>> > Subject: Debuging an Applet
>> >
>> > Hi,
>> >
>> > SYSTEM: WinNT4SP5, JDK1.3, JDE2.1.6 and JDEbug as debuger
>> >
>> > I'm trying to debug an applet, running the applet from jde works fine.
>> >
>> > I start with : JDE->Debug Applet
>> >
>> > It brings up the appletviewer window and that shows at left bottom
>> > corner
>> > 'loading applet'
>> > and then
>> > 'applet startet'
>> >
>> > The debug window shows :
>> >
>> > /---------------
>> > cd d:/RJocham/CodeExamples/javabeansexamples/chapter8/
>> > appletviewer -debug Applet.html
>> >
>> > Initializing jdb...
>> > > Deferring breakpoint SimulatorSample.init.
>> > It will be set after the class is loaded.
>> > > run sun.applet.Main Applet.html
>> > Java HotSpot(TM) Client VM warning: Setting of property "java.compiler"
>> > is ignored
>> > >
>> > VM Started: Set deferred breakpoint SimulatorSample.init
>> > /-----------------
>> >
>> > That's the end of the stoy nothing more happens ....
>> >
>> > Thanks for any help
>> >
>> > Ralph
>> >
>> > --
>> > ___________________________________________________________________
>> >
>> > The Internet Changes Everything
>> > iSolutions
>> > ___________________________________________________________________
>> > Ralph Jocham e-mail: [EMAIL PROTECTED]
>> > Software Engineer phone : (44) 0118 92 43991
>> > Oracle Parkway, Building 520
>> > Thames Valley Park, Reading RG6 1RA
>> > ______________________________________________ __ __ _ __ . __
>> > Opinions are my own and not those of... (__)|-</-\(__ |__(-_
>
>--
>___________________________________________________________________
>
> The Internet Changes Everything
> iSolutions
>___________________________________________________________________
>Ralph Jocham e-mail: [EMAIL PROTECTED]
>Software Engineer phone : (44) 0118 92 43991
>Oracle Parkway, Building 520
>Thames Valley Park, Reading RG6 1RA
>______________________________________________ __ __ _ __ . __
>Opinions are my own and not those of... (__)|-</-\(__ |__(-_
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
