为什么Java会忽略选项"-XX:ErrorFile =/dev/null"? [英] why java ignored option "-XX:ErrorFile=/dev/null"

问题描述

我想防止JVM生成崩溃日志文件，所以我的启动脚本看起来像这样

I want to prevent JVM generating crash log files, so my startup script looks like this

java -XX:ErrorFile=/dev/null MyClass

但是当jvm崩溃时，日志文件'hs_err_pidXXXXX.log'仍会在当前工作目录中生成.为什么?

but when a jvm crash occurs, the log file 'hs_err_pidXXXXX.log' is still generated in current working directory. why ?

操作系统:ubuntu 18.04，Java版本:oracle java 10

OS: ubuntu 18.04, java version: oracle java 10

推荐答案

如果指定给-XX:ErrorFile的文件存在或无法打开，则JVM将退回到默认的hs_err_pid错误文件路径.由于/dev/null可能存在，因此可以解释此行为.

If the file specified to -XX:ErrorFile exists, or can't be opened, then the JVM falls back to the default hs_err_pid error file path. Since /dev/null probably exists, that could explain this behaviour.

我已经浏览了与Oracle的HotSpot对应的OpenJDK JVM源代码，并且在这方面的错误报告代码中似乎没有对/dev/null的任何特殊处理.

I've browsed the OpenJDK JVM source code, corresponding to Oracle's HotSpot, and there doesn't seem to be any special handling of /dev/null in the error reporting code in this respect.

有关JVM维护者的更多详细信息和评论，请参阅以下OpenJDK错误报告: https://bugs.openjdk.java.net/browse/JDK-8189672

For more details and comments from JVM maintainers, see this OpenJDK bug report: https://bugs.openjdk.java.net/browse/JDK-8189672

这篇关于为什么Java会忽略选项"-XX:ErrorFile =/dev/null"?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！