staffan.larsen at oracle.com
Fri Apr 1 01:44:50 PDT 2011
Not a known issue as far as I know, but I found the problem. When we are
creating the dump as a result of an assert failure, the exception
information that is sent to MiniDumpWriteDump is NULL. This causes
MiniDumpWriteDump to fail.
I will file a bug.
On 2011-03-31 23:25, Tom Rodriguez wrote:
> I just tried to use CreateMinidumpOnCrash on Windows x64 and got an empty dump file and an empty failure message.
> -rwxr-xr-x 1 root None 7421 Mar 31 14:00 hs_err_pid4524.log
> -rwxr-xr-x 1 root None 0 Mar 31 14:00 hs_err_pid4524.mdmp
> # A fatal error has been detected by the Java Runtime Environment:
> # Internal Error (C:\temp\jprt\P1\B\181946.never\source\src\share\vm\opto\callGenerator.cpp:1021), pid=4524, tid=8080
> # assert(ok) failed: must always be cold
> # JRE version: 7.0-b135
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (21.0-b05-internal-201103311819.never.baseline-fastdebug mixed mode windows-amd64 com
> pressed oops)
> # Failed to write core dump.
> As far as I can tell it should be impossible to get an empty error message for this. Is this a known issue?
More information about the hotspot-runtime-dev