JDK-8269770 : nsk tests should start IOPipe channel before launch debuggee - Debugee.prepareDebugee
Type:Sub-task
Component:core-svc
Sub-Component:debugger
Priority:P4
Status:Resolved
Resolution:Fixed
OS:generic
CPU:generic
Submitted:2021-07-01
Updated:2024-09-10
Resolved:2021-08-31
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.
148 tests use Debugee.prepareDebugee() method to launch debuggee.
The method launch debuggee, creates IOPipe, resumes debuggee and waits "ready" notification.
Comments
A pull request was submitted for review.
Branch: master
URL: https://git.openjdk.org/jdk17u-dev/pull/2850
Date: 2024-09-06 10:23:05 +0000
06-09-2024
Fix request [17u]
I backport this for parity with 17.0.14-oracle.
No risk, only a test change.
Clean backport.
Test calling prepareDebugee passes.
A lot of tests (about 250) do the same as Debugee.prepareDebugee(), but implement it by themselves:
Debugee debugee = binder.bindToDebugee(...);
IOPipe pipe = debugee.createIOPipe();
debugee.redirectStderr(...);
debugee.resume();
<read string from IOPipe, expect it to be "ready">
Start IOPipe listening from DebugeeProcess.createIOPipe() will fix both scenarios