By sbohne on Feb 26, 2007
It produces the same output as the command-line version. Decoding the crash log is invariably the first step in HotSpot crash diagnosis, yielding the error ID and symbolic information for some of the native stack frames. In addition to providing insight into the root cause of the crash, it can also be useful to compare decoded crash logs with existing bug reports and potentially find a workaround for the crash.
- It only works with crash logs from 5.x or 6.x FCS binaries (no beta, ea, interim or developer builds.)
- This interface is completely unsupported and subject to change or removal at any time.