RFR: 8338883: Add core dump info to -Xlog:os=info [v5]
Gerard Ziemski
gziemski at openjdk.org
Wed Sep 11 16:50:05 UTC 2024
On Tue, 10 Sep 2024 15:03:23 GMT, Gerard Ziemski <gziemski at openjdk.org> wrote:
>> We add a small feature, which adds core dump info, which till now was only printed as part of hs_err log file, directly to stdout, when desired using log mechanism, i.e. `-Xlog:os=info`
>>
>> For example, if we see:
>>
>> `core dump info: core.28283`
>>
>> we know all is set up correctly and we can expect a core file if java process crashes. If we see:
>>
>> `core dump info: Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again`
>>
>> instead, however, we know that "ulimit -c unlimited" needs to be set.
>>
>> Testing:
>> - passes `"MACH5 runtime/ErrorHandling/CreateCoredumpOnCrash.java"`
>> - full MACH5 test in progress...
>
> Gerard Ziemski has updated the pull request incrementally with one additional commit since the last revision:
>
> fix PATH_MAX on Windows, use check_only for record_coredump_status
I see this in hotspot, for example:
if (UseCRC32 && !VM_Version::supports_crc32()) {
warning("UseCRC32 specified, but not supported on this CPU");
FLAG_SET_DEFAULT(UseCRC32, false);
}
so I feel that we would be justified in printing a warning under the circumstances Thomas has outlined.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/20734#issuecomment-2344161704
More information about the hotspot-runtime-dev
mailing list