unny you should ask that as im just sitting doing the same thing - and I got an answer :)
Start your java application with a -classic option to disable HotSpot - then it runs smooth! A while ago I posted some fixes/suggestions for changes in JDE to ensure that debugged applications started from JDE ran in classic mode, but I do not know if these changes have made it into the codebase yet.... But the solution is to just start your java app externally from e.g. Ant or a simple commandline and then just attach to the JVM from JDebug. With hope Max ""Scott Evans"" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I finally got fed up trying to debug servlet-type processes with > println statements so I'm going "debugger". I got jdb working okay > but of course its interface is a little clunky, especially compared > to a nice in-your-editor display. > > So I set up JDEbug and gave it a go. Right away I said "yes! this > rocks!" but unfortunately the performance seems pretty awful compared > to command-line jdb. Variable queries take ~30 seconds to come back; > stepping from line to line is very slow as well. This all works as > one might expect (i.e. "quickly") in command-line jdb. > > I'm running on Win2000, using shared memory to attach to a running > process. > > Is this known behavior for JDEbug? If not, any advice? > > (I haven't tried jdb under JDE yet but I'm about to.) > > Thanks! > > > > scott >
