JDB problems with glibc2 jdk1.2
I'm running the jdk12-pre-v2 for glibc2, and tried to use jdb. I got
the following error:
~/work/KidPad-July-14/kidpad $ jdb
Initializing jdb...
[debugger: starting child: /usr/local/jdk12_pre-v2_test/jre/bin/java -Xdebug -Djava.compiler=NONE -Xbootclasspath/a:/usr/local/jdk12_pre-v2_test/lib/tools.jar sun.tools.agent.EmptyApp]
Reaped pid = 2074, status = 1
[Internal debugger error: Failed to exec a child java interpreter with this command line: /usr/local/jdk12_pre-v2_test/jre/bin/java -Xdebug -Djava.compiler=NONE -Xbootclasspath/a:/usr/local/jdk12_pre-v2_test/lib/tools.jar sun.tools.agent.EmptyApp]
Exception in thread "main" java.lang.InternalError
at sun.tools.debug.RemoteAgent.error(RemoteAgent.java:1409)
at sun.tools.debug.RemoteAgent.<init>(RemoteAgent.java:243)
at sun.tools.debug.RemoteDebugger.<init>(RemoteDebugger.java:63)
at sun.tools.ttydebug.TTY.<init>(TTY.java:1633)
at sun.tools.ttydebug.TTY.main(TTY.java:1809)
Somehow the arguments get mangled (i.e. the -Xbootclasspath/a:/usr/...
argument). When I substitute -classpath /usr/... it works fine. Any
idea of how/why jdb is mangling the argument info?
jas.
--NAA05174.933623959/cleveland.ncgr.org--
Reply to: