At 08:28 PM 9/11/00 +0200, Mattias Waldau wrote:
>As you can see below, it helps to press return. However, the debugger
>still doesn't work for me.
>
>Do we actually know that JDE works with JDK 1.3 on Windows 2000?
>
>/mattias
>
>
>cd c:/data/java/se/waldau/
>javaw -classpath
>c:/data/emacs/site/jde-2.2.3/java/lib/jde.jar;c:/jdk1.3/lib/tools.jar
>jde.debugger.Main
>
>
>(jde-dbo-init-debug-session)
>
>JDE> -1 1 launch 1 -vmexec javaw -home c:\jdk1.3 -classic
>se.waldau.encodePassword
>
>
>(jde-dbo-message 1 "VM options: '-classic '")
>
>
>(jde-dbo-message
>1 "Launched VM Java Debug Interface (Reference Implementation) version 1.3
>Java Debug Wire Protocol (Reference Implementation) version 1.0
>JVM Debug Interface version 1.0
>JVM version 1.3.0 (Classic VM, native threads, nojit)")
>
>
>(jde-dbo-message 1 "initSIOConnect: starting standard I/O handshake.")
>
>
>(jde-dbo-event-set
>1 "all"
>(list "Thread" 1 "main" "runnable" "suspended by debugger"
>(list)
>(list)
>nil)
>(list 'jde-dbo-vm-start-event))
>
>
>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>%%% after pressing return a couple of times I get
>
>
>
>(jde-dbo-message 1 "initSIOConnect: starting SIO connect thread.")
>
>
>(jde-dbo-command-result 1 1379)
>
>
>(jde-dbo-message
>1 "Debugger waiting for Emacs to connect to app SIO port 1379.")
Hit return again here. I think the problem is that for some reason on some
Windows systems (frustratingly, never on mine), the debugger's standard
output buffer is not getting flushed. This problem has cropped up before in
other contexts where Emacs has to communicate with an external process,
using process standard I/O (i.e., pipes). Perhaps hitting return touches
off a chain of events that results in the Java I/O code deciding to flush
the standard output buffer of the JDEbug process.
Please let me know if this works.
- Paul
