Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4670964

jdbx is broken from Hopper-B03 onward

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 1.4.1
    • Fix Version/s: None
    • Component/s: vm-legacy
    • Labels:
      None
    • Subcomponent:
    • CPU:
      generic
    • OS:
      solaris

      Description

      ###@###.### 2002-04-18

      jdbx is broken using Hopper-B09 on Solaris SPARC (2.8). The failure
      mode with the java command is:

      (dbx) debug Values.class
      Debug target is "Values.class"
      Will be debugging "Values"
      (dbx) stop in Values.main
      (2) java stop in Values.main(java.lang.String[])
      (dbx) run
      AgentThread:cb_suspend():JVMDI_SuspendThread() failed -- INVALID_THREAD
      AgentThread: cb_resume(): JVMDI_ResumeThread() failed -- INVALID_THREAD
      Test: hello
      Test: hook
      Test: goodbye
      AgentThread:cb_suspend():JVMDI_SuspendThread() failed -- INVALID_THREAD
      AgentThread:cb_suspend():JVMDI_SuspendThread() failed -- INVALID_THREAD
      AgentThread: cb_resume(): JVMDI_ResumeThread() failed -- INVALID_THREAD
      AgentThread: cb_resume(): JVMDI_ResumeThread() failed -- INVALID_THREAD
      TMap_end(): handle mismatch
      AgentThread: JVMDI_GetObjectHashCode() failed -- INVALID_OBJECT
      TMap_end(): handle mismatch

      execution completed, exit code is 1

      The failure mode with the java_g command is worse:

      Debug target is "Values.class"
      Will be debugging "Values"
      dbx: Unable to start the Java virtual machine
      (dbx) AgentThread: JVM_OnLoad(): debugger not attaching

      The failure modes with main/baseline as of 2002.04.18 AM (including the
      fix for 4657650) appears to be the same.


      ###@###.### 2002-04-19

      Narrowing down the various jdbx breakages in Hopper (Solaris SPARC (2.8)):

      B01 jValues and jarray_basic_1 - java/java_g PASS
      B02 jValues and jarray_basic_1 - java/java_g PASS
      B03 jValues - java HANG or INVALID_THREAD, java_g can't start
      B03 jarray_basic_1 - java HANG or INVALID_THREAD, java_g INVALID_THREAD
      B04 jValues and jarray_basic_1 - java/java_g INVALID_THREAD
      B05 jValues - java/java_g INVALID_THREAD
      B05 jarray_basic_1 - java INVALID_THREAD, java_g can't start
      B06 jValues - java INVALID_THREAD, java_g can't start
      B06 jarray_basic_1 - java/java_g INVALID_THREAD
      B07 jValues and jarray_basic_1 - java/java_g INVALID_THREAD
      B08 jValues and jarray_basic_1 - java INVALID_THREAD, java_g can't start
      B09 jValues and jarray_basic_1 - java INVALID_THREAD, java_g can't start

      As of kbr's putback to main/baseline at 20020419034751, the failure mode
      is the same:

      jValues and jarray_basic_1 - java INVALID_THREAD, java_g can't start

      This means that jdbx will be broken in B10 which is about to be promoted
      and will also be broken in B11 which just got pushed for a pre-integration
      test cycle.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dcubed Daniel Daugherty
                Reporter:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: