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

TTY: jdb does not set valid thread group as default

    XMLWordPrintable

Details

    • generic
    • generic, solaris

    Description



      Name: dkR10014 Date: 11/05/2001


       The jdb from jdk1.4.0 fails to pass the test against "threadgroup" command.
      The test works as follows.

      The number of threads are created in two named ThreadGroup(s) in the
      debugged test application. The jdb stops the debugeed application at
      given breakpoint and then lists all existing thread groups upon
      "threadgroups" command. Then two "threadgroup <thread_group_name>"
      commands try to set up application's thread groups as default.
      But the jdb message:
        "myGroup-..." is not a valid threadgroup name.
      is received.
        
      This failure is observed on all platforms - Solaris, Linux, Windows.
      The jdb from jdk1.4.0-beta3-b84 build was tested.

      Steps to reproduce the bug:
      1. cd /net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/{this bug ID}
      2. sh doit.sh {JAVA_HOME} {PERL5_PATH}

      where JAVA_HOME is for jdk1.4.0 and PERL5_PATH is path to perl5 binary.

      This bug affects the following testbase_nsk test:
         nsk/jdb/threadgroup/threadgroup001
          
      ======================================================
      Below is the jdb input command scenario:

      stop at ThreadGroupTest:116
      run ThreadGroupTest
      threadgroups
      threadgroup myGroup-0
      threads
      threadgroup myGroup-1
      threads
      cont

      ======================================================
      Below is the jdb output redirected to X.debug.out file.
      It shows that there is a tail of null symbols after name of thread group
      in a "threadgroups" and "threads" commands' output.
       
      Initializing jdb ...
      > Deferring breakpoint ThreadGroupTest:116.
      It will be set after the class is loaded.
      > run ThreadGroupTest
      >
      VM Started: Set deferred breakpoint ThreadGroupTest:116

      Breakpoint hit: "thread=main", ThreadGroupTest.main(), line=116 bci=249
      116 int i = 0; // a dummy statement. acts as a breakpoint.

      main[1] 1. (java.lang.ThreadGroup)0x12d system
      2. (java.lang.ThreadGroup)0x12e main
      3. (java.lang.ThreadGroup)0x130
      myGroup-0<null><null><null><null><null><null><null>
      4. (java.lang.ThreadGroup)0x131
      myGroup-1<null><null><null><null><null><null><null>
      main[1] "myGroup-0" is not a valid threadgroup name.
      main[1] Group system:
        (java.lang.ref.Reference$ReferenceHandler)0xf5 Reference Handler cond. waiting
        (java.lang.ref.Finalizer$FinalizerThread)0xf4 Finalizer cond. waiting
        (java.lang.Thread)0xf2 Signal Dispatcher running
        (java.lang.Thread)0xf3 CompileThread0 cond. waiting
      Group main:
        (java.lang.Thread)0x1 main running (at
      breakpoint)
        (java.util.logging.LogManager$Cleaner)0x12f Thread-0 unknown
      Group myGroup-0<null><null><null><null><null><null><null>:
        (t)0x12c myThread-0 cond. waiting
        (t)0x132 myThread-1 running
        (t)0x133 myThread-2 running
        (t)0x134 myThread-3 running
        (t)0x135 myThread-4 running
      Group myGroup-1<null><null><null><null><null><null><null>:
        (t)0x136 myThread-5 running
        (t)0x137 myThread-6 running
        (t)0x138 myThread-7 running
        (t)0x139 myThread-8 running
        (t)0x13a myThread-9 running
      main[1] "myGroup-1" is not a valid threadgroup name.
      main[1] Group system:
        (java.lang.ref.Reference$ReferenceHandler)0xf5 Reference Handler cond. waiting
        (java.lang.ref.Finalizer$FinalizerThread)0xf4 Finalizer cond. waiting
        (java.lang.Thread)0xf2 Signal Dispatcher running
        (java.lang.Thread)0xf3 CompileThread0 cond. waiting
      Group main:
        (java.lang.Thread)0x1 main running (at
      breakpoint)
        (java.util.logging.LogManager$Cleaner)0x12f Thread-0 unknown
      Group myGroup-0<null><null><null><null><null><null><null>:
        (t)0x12c myThread-0 cond. waiting
        (t)0x132 myThread-1 running
        (t)0x133 myThread-2 running
        (t)0x134 myThread-3 running
        (t)0x135 myThread-4 running
      Group myGroup-1<null><null><null><null><null><null><null>:
        (t)0x136 myThread-5 running
        (t)0x137 myThread-6 running
        (t)0x138 myThread-7 running
        (t)0x139 myThread-8 running
        (t)0x13a myThread-9 running
      main[1] > myThread-3 returns 10000
      myThread-1 returns 10000
      myThread-2 returns 10000
      myThread-0 returns 10000
      myThread-4 returns 10000
      myThread-5 returns 10000
      myThread-6 returns 10000
      myThread-7 returns 10000
      myThread-8 returns 10000
      myThread-9 returns 10000

      The application exited

      ------------------------------------------------------

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

      Name: dkR10014 Date: 01/13/2003


      This bug also affects the following testbase_nsk test:
         nsk/jdb/threadgroup/threadgroup002


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

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kdossunw Kdos Kdos (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: