| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2037650 | 1.4.0 | Daniel Daugherty | P2 | Resolved | Fixed | beta |
This bug is caused by the combination of two JVMDI problems:
GetAllThreads should only return running threads, however it is now
returning newly created, not yet started threads.
If, as is typical for any debugger, the debugger in question, queries
the status of the returned threads, with GetThreadStatus, the
GetThreadStatus function will return JVMDI_ERROR_INVALID_THREAD, when
passed the new thread - this error bubbles up to the JDI level as
an InternalError. This error should only be returned when what is
passed is , in fact, not a thread at all. There is no good thread
status to return, leaving JVMDI_THREAD_STATUS_UNKNOWN as the only
option.
Both problems should be fixed.
robert.field@Eng 2000-10-12
GetAllThreads should only return running threads, however it is now
returning newly created, not yet started threads.
If, as is typical for any debugger, the debugger in question, queries
the status of the returned threads, with GetThreadStatus, the
GetThreadStatus function will return JVMDI_ERROR_INVALID_THREAD, when
passed the new thread - this error bubbles up to the JDI level as
an InternalError. This error should only be returned when what is
passed is , in fact, not a thread at all. There is no good thread
status to return, leaving JVMDI_THREAD_STATUS_UNKNOWN as the only
option.
Both problems should be fixed.
robert.field@Eng 2000-10-12
- backported by
-
JDK-2037650 exception: GetAllThreads returns not yet running thread / GetThreadStatus chokes
-
- Resolved
-
- duplicates
-
JDK-4406647 JPDA thread info incorrect
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
JDK-4232338 JDWP: Need new thread status for not-yet-started threads
-
- Closed
-