JDK-6579357 : JDWP: Commands that require threads to be suspended may not return correct error codes
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2007-07-11
  • Updated: 2023-12-14
  • Resolved: 2016-11-04
Related Reports
Relates :  
JDK-6525646 - (JDWP) ThreadReference.OwnedMonitorsStackDepthInfo returns invalid error when passed thread is null
Description
Several JDWP commands require that a thread be suspended but do not specify an error code if the thread is not suspended:
  MonitorInfo
  Frames
  FrameCount
  OwnedMonitors
  OwnedMonitorsStackDepthInfo 

Also, these commands 
  ForceEarlyReturn
  PopFrames

require a thread to be suspended, but the error code returned if a thread is not suspended is 
   THREAD_NOT_SUSPENDED	13	If the specified thread has not been suspended by an event.  


If the thread is suspended by a non-event, eg, a suspend command, either the
description of the command is wrong, or the error code is wrong.
Comments
This is not on our list of current priorities. If this changes, please reopen this issue.
04-11-2016