JDK-8076012 : SA don't support flags of type size_t
- Type: Bug
- Component: hotspot
- Sub-Component: svc-agent
- Affected Version: 9
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-03-25
- Updated: 2018-01-17
- Resolved: 2015-03-26
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.
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 9 |
|---|
9 b59Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The flag handling code in the VM class does not know about size_t. This causes problems now when a bunch of flags has been changed to size_t. The VM.Flag.getValue() returns NULL for size_t flags. The result is failures like: WARNING: Hotspot VM version 1.9.0-internal-fastdebug-20150324154453.mgerdin.hs-gc-8075511-gcc-b00 does not match with SA version 1.9.0-internal-fastdebug-20150324154453.mgerdin.hs-gc-8075511-gcc-b00. You may see unexpected results. Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:502) at sun.tools.jmap.JMap.runTool(JMap.java:201) at sun.tools.jmap.JMap.main(JMap.java:130) Caused by: java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:556) at java.lang.Long.parseLong(Long.java:718) at sun.jvm.hotspot.tools.HeapSummary.getFlagValue(HeapSummary.java:259) at sun.jvm.hotspot.tools.HeapSummary.run(HeapSummary.java:70) at sun.jvm.hotspot.tools.Tool.startInternal(Tool.java:260) at sun.jvm.hotspot.tools.Tool.start(Tool.java:223) at sun.jvm.hotspot.tools.Tool.execute(Tool.java:118) at sun.jvm.hotspot.tools.HeapSummary.main(HeapSummary.java:49) ... 6 more java.lang.RuntimeException: Test FAILED jmap exits with non zero exit code 1 at JMapHeapConfigTest.main(JMapHeapConfigTest.java:150) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:502) at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92) at java.lang.Thread.run(Thread.java:745) JavaTest Message: Test threw exception: java.lang.RuntimeException: Test FAILED jmap exits with non zero exit code 1
Comments
|