JDK-8177072 : vmassert_status is active in product builds
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2017-03-18
  • Updated: 2017-03-18
  • Resolved: 2017-03-18
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 9
9Resolved
Related Reports
Duplicate :  
JDK-8165358 - vmassert_status is not debug-only
Relates :  
JDK-8148425 - strerror() function is not thread-safe
Description
Before JDK-8148425: "strerror() function is not thread-safe",  the vmassert_status macro was defined unconditionally, but in terms of the vmassert macro, which was empty in product builds.

8148425 needed to move the use of strerror into debug.cpp to avoid including os.hpp in debug.hpp, and so a report_vm_status_error method was added similar to report_vm_error. The vmassert_status macro was expanded to call report_vm_status_error but in doing so overlooked the fact that vmassert_status should be a no-op in product builds.
Comments
Impact: code bloat in product binary, performance overhead of additional error checking, possibility of asserting in product builds. M Likelihood: always present: H Workaround: none: H P2
18-03-2017