ingrid.yao@Eng 2001-08-09

J2SE Version (please include all output from java -version flag):
  Java(TM) 2 Runtime Environment, Standard Edition (build
  1.4.0-beta_refresh-b72)

  Java Debug Wire Protocol (Reference Implementation) version 1.4
  JVM Debug Interface version 1.2
  JVM version 1.4.0-beta_refresh (Java HotSpot(TM) Client VM, interpreted mode)

Does this problem occur on J2SE 1.3?
  No

Operating System Configuration Information (be specific):
  Windows 2000, Service Pack 1

Hardware Configuration Information (be specific):
  Intel Pentum III, 1ghz, 512mb

Bug Description:
  synopsis: suspend on vm-level does not suspend all threads

  suspending all threads through JDWP (VirtualMachine cmd set, Suspend cmd)
  does leave one thread named 'Thread-0' running. it is the first child
  thread of the 'Main' thread group and cannot be debugged.

Steps to Reproduce (be specific):
  1. connect to the target vm (e.g. the debugee)
  2. suspend the execution at vm level using the "Suspend command"
     (VirtualMachine cmd set)
  3. enumerate all threads of the 'Main' thread group by using the
     "AllThreads command"(ThreadGroupReference cmd set, Children cmd)
  4. check the status of the returned threads using the "Status command"
     (ThreadReference cmd set)
  and you will see that there's one thread named "Thread-0" which is
  not suspended.

  It sounds like this thread is a JPDA-related system thread which
  normally should not be returned by the "AllThreads command"
  and the thread-group "Children command"