JDI: Sun Launcher does not tokenize 'str1"str2"' correctly

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 1.3.0
    • Affects Version/s: 1.3.0
    • Component/s: core-svc
    • kestrel
    • generic
    • generic
    • Not verified

      We found a problem with launching debugger using the defaultConnector.
      If the Connector.Argument of type "options" has quoted string in it,
      defaultConnector.launch will remove the quote and generates an invalid command
      line. (happens in Solaris and WinNT)

      e.g.:
        add the following VM parameter to the defaultConnector "options" argument.
         -Duser.dir="E:\JBuilder3\myprojects\untitled5"

      The resulted command line will be:
        -Duser.dir= E:\JBuilder3\myprojects\untitled5 (there is a space between
      '=' and 'E')




      The following is the exception thrown by the defaultConnector launcher:

      com.sun.jdi.connect.VMStartException: VM initialization failed for:
      D:\jdk1.2.2\bin\javaw -classic -Duser.dir= E:\JBuilder3\myprojects\untitled5
      -classpath

      E:\JBuilder3\myclasses;E:\pt\lib\jbcl3.0.jar;E:\pt\lib\jbcl3.0-res.jar;D:\jdk1.2.2\jre\lib\rt.jar;D:\jdk1.2.2\jre\lib\i18n.jar;D:\jdk1.2.2\lib\dt.jar;D:\jdk1.2.2\lib\tools.jar;D:\jdk1.2.2\lib\jpda.jar
      -Xdebug -Xnoagent -Djava.compiler=NONE
      -Xrunjdwp:transport=dt_shmem,address=javadebug,suspend=y untitled5.untitled5

      This problem occurs when a single command line argument is partially quoted, i.e. the -Duser.dir and the "E:\..." belong together but are separated into separate tokens.

            Assignee:
            Robert Field (Inactive)
            Reporter:
            Gordon Hirsch (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: