Bug ID: JDK-8173896 SA: BasicLauncherTest.java (printmdo) fails for Client VM and Server VM with emulated-client

JDK-8173896 : SA: BasicLauncherTest.java (printmdo) fails for Client VM and Server VM with emulated-client

Type: Bug
Component: hotspot
Sub-Component: svc-agent
Affected Version: 9,10

Priority: P3
Status: Resolved
Resolution: Fixed
OS: generic
CPU: generic

Submitted: 2017-02-03
Updated: 2018-01-17
Resolved: 2017-02-15

Versions (Unresolved/Resolved/Fixed)

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.

To download the current JDK release, click here.

JDK 10	JDK 9
10Fixed	9 b159Fixed

Related Reports

Relates :	JDK-8175054 - Move new TestPrintMdo.java to hotspot/test directory
Relates :	JDK-8166002 - Emulate client build on platforms with reduced virtual address space
Relates :	JDK-8175512 - new TestPrintMdo.java fails with -XX:TieredStopAtLevel=1
Relates :	JDK-8175818 - hotspot/test/serviceability/sa/TestPrintMdo.java executed with emulated client build

Description

The 'printmdo' command in BasicLauncherTest.java fails with: 
Execution failed: `main' threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: One or more of 'VirtualCallData', 'CounterData', 'ReceiverTypeData', 'bci', 'MethodData' or 'java/lang/Object' not found

Comments

Method data output is not available for client VMs and emulated-client VMs. Avoid running the test for these cases. Creating a separate test hotspot/test/serviceability/sa/TestPrintMdo.java for better isolation.

11-02-2017