JDK-8282385 : [LOOM] Need test for ThreadReference.stop() on a vthread
Type:Enhancement
Component:core-svc
Sub-Component:debugger
Affected Version:repo-loom
Priority:P3
Status:Resolved
Resolution:Fixed
Submitted:2022-02-25
Updated:2022-03-19
Resolved:2022-03-19
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
We currently have no test that calls ThreadReference.stop() on a vthread.
Comments
This was fixed in the loom repo by https://github.com/openjdk/loom/commit/47929b8656c2d7945fa8b049ffbed93845b4a06f
19-03-2022
I found that vmTestbase/nsk/jdb/kill/kill001 uses ThreadReference.stop(). It also seems to be the only test that triggers the threadControl_interrupt() code in the debug agent (I stuck an assert in it, and this is the only test that triggered the assert).
I did some work to convert kill001 to work with vthreads. It required some addtional vthread support in the Jdb tool. Given that and also the fact that ThreadReference.stop() is not yet supported for vthreads, I tabled the work and checked it into a branch: https://github.com/plummercj/loom/tree/kill001_vthreads