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.