At 10:27 AM 8/7/00 -0700, you wrote: >Hi Paul, > >Sorry to bother you. I put this question on the mailing list, but did not see any suggestion. I am currently working fine with JDE but JDEbug seemed to have a couple of nice features to track variables, from what I see a little in the docs. > > >Message below posted on 8/4. > >I just downloaded jde yesterday. I was able run jde on my Win2K platform. Had to revert to oldjdb as the jde-db-debugger setting. > >Then I read about JDEbug and decided to try it out. But it seems to have some trouble. I have included the displayed messages below. Scanning the web site for FAQ, Trouble Shooting guide etc. I could not find anything. I do remember seeing some note about JDEbug having trouble with HotSpot VM and to not use it, but now I cannot find the same note again on exactly how I was to not use it. The following is excerpted from the JDEbug User's Guide. Please let me know why it failed to convey the information you are seeking so that I can correct the deficiency and thereby avoid wasting time repeating documented information. - paul **************************************************************************** ******************* JDEbug Requirements JDEBug requires a virtual machine that conforms to the specifications of the Java Debug Platform Architecture (JPDA) defined by Sun Microsystems. The vm shipped with Sun's Java SDK 1.3 for Windows and Solaris conform to the JPDA specification. Note JPDA does not run reliably when the JDK 1.3 vm is operating in HotSpot mode. For example, JPDA sometimes fails to stop the debuggee process at breakpoints and has trouble getting the this object of the method in which the debuggee process is currently suspended. Sun's JPDA development team is aware of this problem and is working to provide a solution. Meanwhile, you can work around the problem by running the vm in "classic" mode. To do this, toggle the JDE variable jde-run-classic-mode-vm on. ------------------------------------------------------------ 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
