At 08:00 PM 12/15/99 -0500, Paul Michael Reilly wrote:
>Paul Kinnucan <[EMAIL PROTECTED]> writes:
>
> > * Recompiled the debugger, using javac. Previous versions were compiled
> > with jikes. The jikes version results in a mysterious null pointer
exception
> > when stepping through code.
>
>This change did seem to cure the Blackdown JDK-RC4 crash. For what
>it's worth I was using jikes version 1.03 before I switched back to
>javac. Next I need to understand why the application VM died (Reaped
>message) and how to make JDE deal a little more gracefully with
>messages such as "Reaped pid = 4224, status = 1" as shown in the
>*JDebug* buffer, which follows. Any insight or suggestions on where
>to start looking on either issue would be much appreciated.
>
>Thanks,
>
>-pmr
>
>*JDebug*
>
>java -classpath
/projects/jde/java/lib/jde.jar:/data/pmr/java/jdk/lib/jpda.jar
jde.debugger.Main
>
>
>(jde-dbo-init-debug-session)
>JDE> -1 1 launch 1 -use_executable java -classpath /home/pmr/test -Xms16m
-Xmx96m Test
>
>
>
>Reaped pid = 4224, status = 1
I've never seen this. I have no idea what it means.
>
>(jde-dbo-command-error
>1 "VM initialization failed for: /projects/blackdown/jdk1.2.1/jre/bin/java
-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=hamm.pajato.com:1098,suspend=y
-use_executable java -classpath /home/pmr/test -Xms16m -Xmx96m Test")
>
The above is the command line that jdebug uses to launch your application.
Simply cut and paste the above into a shell and execute. The resulting
error message should provide more insight into what went wrong.
- Paul
