如何在Windows环境下验证Java -XX:ErrorFile参数配置是否生效

Great question! If you need to verify your -XX:ErrorFile configuration on Windows without altering your existing JVM command-line parameters, here are two practical, reliable methods:

Method 1: Use Windows Debugging Tools (cdb/windbg) #

This is the closest equivalent to Linux's kill -SIGSEGV, as it forces the JVM to crash with a fatal error and trigger error log generation.

1. First, install the Windows Debugging Tools — you can get this as a standalone component from the Windows SDK (you don’t need to install the entire SDK, just select the "Debugging Tools for Windows" option during setup).
2. Find the PID of your target java.exe process: Open Task Manager, go to the "Details" tab, locate the java.exe instance you want to test, and note its PID.
3. Open a Command Prompt (or PowerShell) as an administrator, then run:

   cdb -p <your-java-pid>
   

   This attaches the debugger to your Java process.
4. Once the debugger prompt appears, enter this command:

   .crash
   

   This intentionally triggers a fatal exception (similar to SIGSEGV on Linux) in the JVM process.
5. Check the path you specified with -XX:ErrorFile — you’ll find the generated fatal error log there.

Method 2: Use a Lightweight Native Script (Advanced Users) #

If you don’t want to install debugging tools, you can use a PowerShell script that leverages Windows API calls to trigger an access violation in the Java process. Here’s a simplified example:

1. Save the following code as TriggerJvmCrash.ps1:

   param([int]$pid)
   $kernel32 = Add-Type -MemberDefinition @"
       [DllImport("kernel32.dll")]
       public static extern IntPtr OpenProcess(uint dwDesiredAccess, bool bInheritHandle, uint dwProcessId);
       [DllImport("kernel32.dll")]
       public static extern bool DebugActiveProcess(uint dwProcessId);
       [DllImport("kernel32.dll")]
       public static extern bool DebugBreakProcess(IntPtr hProcess);
   "@ -Name Kernel32 -Namespace Win32 -PassThru
   
   $processHandle = $kernel32::OpenProcess(0x001F0FFF, $false, $pid)
   $kernel32::DebugActiveProcess($pid)
   $kernel32::DebugBreakProcess($processHandle)
   

2. Run it as an administrator with your Java PID:

   .\TriggerJvmCrash.ps1 -pid <your-java-pid>
   

   This will force the JVM to crash and generate the error log at your specified path.

Important Notes #

• Always test these methods in a non-production environment — they will terminate the Java process abruptly.
• Ensure the user running the JVM has write permissions for the path specified in -XX:ErrorFile; missing permissions will prevent log generation even if the configuration is correct.

内容的提问来源于stack exchange，提问作者SATO Yusuke