At 11:01 AM 8/31/99 -0400, you wrote:
>Sorry, I thought you still had the information from my mail yesterday
>morning.
>I hadn't wanted to clutter up your mail.
>
I'd prefer to get all the information, especially the JDEbug buffer, for
two reasons: You may have changed something and so I don't have to go
hunting back through my mail (I get a lot).
Anyway, the JDEBug buffers tells me three things:
1) The debugger did indeed start.
2) The debugger tried to start your application but the vm that is
running the application could not find its class.
3) The command line used to launch your app did not contain
a classpath.
Your environment variables file tells me that your CLASSPATH
variable is set. So why isn't the VM finding your application?
I believe the problem is that the vm is a subprocess of a subprocess
and may not be getting the CLASSPATH from the grandparent process,
i.e., emacs.
In the previous betas, the JDE looked to see if your CLASSPATH
env. variable was defined and, if so, included it on the command-line.
In this release I changed things so that JDEbug uses the same
function to construct the command-line args as does jdb. Unfortunately,
that function does not check to see if CLASSPATH is defined. It
considers only the settings of jde-db-option-classpath and
jde-global-classpath. I will fix this in the next release.
Meanwhile, try setting jde-global classpath to your classpath.
- Paul
>JDEBUG Buffer is below. The rest of the files are attachd. prj.el is new
>with updated time(10 seconds moving to 50) The est is the same....
>-Dave
>
>javaw -classpath
>d:/emacs-20.4/lisp/jde-2.1.6beta8/java/lib/jde.jar;D:/jpda/bin/lib/jpda.jar
>jde.debugger.Main
>
>JDE> -1 1 launch 1 -use_executable javaw -v -verbosegc -verbosejni SimplCon
>
>
>
>(jde-dbo-init-debug-session)
>
>java.lang.NoClassDefFoundError: com/sun/jdi/ClassNotLoadedException
> at jde.debugger.Jdebug.initApplication(Jdebug.java:387)
> at jde.debugger.Jdebug.doLaunch(Jdebug.java:437)
> at jde.debugger.Jdebug.handleGeneralCommand(Jdebug.java:278)
> at jde.debugger.Jdebug.access$0(Jdebug.java:260)
> at jde.debugger.Jdebug$1.run(Jdebug.java:210)
>
>> -----Original Message-----
>> From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, August 31, 1999 10:20 AM
>> To: David Kuchta
>> Subject: RE: Debugger timeout with b8
>>
>>
>> At 10:00 AM 8/31/99 -0400, you wrote:
>> >Paul-
>> >
>> > I moved to timeout setting up to 25 then 50 seconds and still
>> got the same
>> >result...
>> >At this point I believe that jdebug is really not running.
>> >
>> >Naive question of the day: Is there supposed to be a jdebug.exe
>> somewhere?
>>
>> No. JDEbug is a Java application. The JDE runs it just like it runs any
>> other Java application, by invoking a VM on its main class.
>>
>> >If I search for jdebug.* I find jdebug.java, but no class except inside
>> >D:\emacs-20.4\lisp\jde-2.6beta8\java\lib\jde.jar.
>> >
>> >I've since put the jar on my class path to no avail...
>>
>> You don't need to do this.
>>
>> >Sorry for the bother...
>>
>> You could make things a lot easier for me by providing all relevant info
>> including your .emacs file and the JDEBug buffer in your email. The JDEBug
>> buffer provides a complete transcript of the session, making it possible
>> for me to figure out what is going on without having to play
>> twenty questions
>> with you.
>>
>> - Paul
>>
>>
>
>
>
>
>
