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

JDI: com.sun.jdi.ThreadReference.THREAD_STATUS_NOT_STARTED never seen

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 1.4.1
    • core-svc
    • None
    • generic
    • generic



      Name: tb29552 Date: 04/12/2002


      While working on a test for a different bug, I wrote
      a program that created several threads but did not start
      them. The situation looked like this in jdb:

      > threads
      Group system:
        (java.lang.ref.Reference$ReferenceHandler)0x2 Reference Handler cond. waiting
        (java.lang.ref.Finalizer$FinalizerThread)0x3 Finalizer cond. waiting
        (java.lang.Thread)0x4 Signal Dispatcher running
        (java.lang.Thread)0x5 CompileThread0 cond. waiting
      Group main:
        (java.lang.Thread)0xa main running
        (java.util.logging.LogManager$Cleaner)0xb Thread-0 unknown
        (RunnerThread)0xc stdin 1 unknown
        (RunnerThread)0x12 stdin 2 unknown
        (RunnerThread)0x13 stdin 3 unknown
        (RunnerThread)0x14 stdin 4 unknown

      The "RunnerThread" above are not started, but jdb shows a
      status of "unknown" and won't give out any other hints:

      > thread 0x14
      "0x14" is not a valid thread id.

      Looking at the code, I don't see any provision for taking advantage
      of com.sun.jdi.ThreadReference.THREAD_STATUS_NOT_STARTED. I don't
      know if it is passed up properly.

      ======================================================================

            Unassigned Unassigned
            tbell Tim Bell
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: