Sometime before lunch I figured this out - according to some dude on the internet[1] you have to start the interpreter like this:
java -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n -Djava.compiler=NONE Now why didn't *I* think of that? *Much* better than the old "-debug" switch. Not. This apparently changed between Java 1 and Java 2, and our man pages are Java 1-ish even though I'm using something Java 2-ish for the JVM. -Ken [1] http://www.ncsa.uiuc.edu/UserInfo/Resources/Hardware/IBMp690/IBM/usr/idebug/ help/en_US/debugwks/tasks/tbwattjv.htm -----Original Message----- From: Williams, Ken [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 11:05 AM To: 'Patrick LeBoutillier' Cc: Inline mailing list (E-mail) Subject: RE: Using the Java debugger Hmm, it looks like this may not be an Inline::Java problem - even my HelloWorld standalone Java class doesn't seem to do anything when I pass it the -debug flag: [sol2:~/src/gate_bug] % java HelloWorldApp Hello World! [sol2:~/src/gate_bug] % java -debug HelloWorldApp Hello World! [sol2:~/src/gate_bug] % java -deug HelloWorldApp Unrecognized option: -deug Could not create the Java virtual machine. So I guess I need to nail down this issue with the jvm first, then get it working with Inline. -Ken
