At 06:14 PM 11/16/99 -0800, Thanh Nguyen wrote:
>Content-Type: TEXT/plain; charset=us-ascii
>Content-MD5: yXIYnrr24/PUq3IvtE35og==
>
>
>Hi,
>I am running XEmacs 20.4 on Solaris 7 and JDE 2.6beta11. It seems that I have
>a setup problem some where that I can't figure out based on the documents
>I read. Thanks for any hints.
>Regards.
>thanh
>
>
>
>The *JDEbug* buffer is showing the following error when I try to debug an app:
>
>
>java -classpath
>/net/capra/export16/thanh/Xemacs/jde/jde-2.1.6beta11/java/lib/jde.jar:/net/c
>apra
>/export16/thanh/Xemacs/jde/lib/jpda.jar jde.debugger.Main
>
>
>(jde-dbo-init-debug-session)
>
>JDE> -1 1 launch 1 -use_executable java -classpath .:pixtran.jar
>-Djava.compiler= Viewer
^^^^^^^^^^^^^^^^
What is this?
>
>
>
>(jde-dbo-debug "
>com.sun.jdi.VMDisconnectedException: Bad file number
^^^^^^^^^^^^^^^^
> at com.sun.tools.jdi.TargetVM.send(TargetVM.java:271)
> at
>com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:696)
> at com.sun.tools.jdi.PacketStream.send(PacketStream.java:55)
> at
>com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.enqueueCommand(JDWP.java:476)
> at com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.process(JDWP.java:467)
> at
>com.sun.tools.jdi.VirtualMachineImpl.<init>(VirtualMachineImpl.java:174)
> at
>com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMach
>ineM
>anagerImpl.java:166)
> at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:121)
> at
>com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:
>153)
> at jde.debugger.Application.launch(Application.java:363)
> at jde.debugger.Application.initialize(Application.java:163)
> at jde.debugger.Jdebug.initApplication(Jdebug.java:403)
> 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)
>")
>
>
>(jde-dbo-command-error
>1 "Unspecified error: com.sun.jdi.VMDisconnectedException: Bad file number")
>
This "Bad file number" error prevented JPDA from launching your application.
I wonder if this is a socket problem. Debugging with JDEBug entails several
sockets. JDEbug uses a socket channel to pass standard I/O between Emacs
and the debuggee application. I believe JPDA uses a socket to communicate
between itself and the VM running the debuggee app. Perhaps there is some
conflict with existing sockets. You might want to try specifying another
socket number, using the JDEBug Preferences menu.
- Paul
