RFO: a tool to analyze HotSpot fatal error logs

[Maxim Kartashev]

Hello,

I am writing to inquire about the potential interest of the people involved
in inspecting HotSpot crashes in a tool aimed at facilitating that
inspection.

We at JetBrains have developed an internal plugin that helps both with
filtering through dozens of reports quickly in order to find a pattern and
for diving deep into a particular crash. In addition to the "standard"
features such as syntax highlighting, folding, and structural navigation,
it will
* highlight potential problems such as overloaded CPU, low physical memory,
the presence of OOME in the recent exceptions, LD_LIBRARY_PATH being set,
etc,
* generate an "executive summary" for a high-level overview, for example,
by front-line support,
* pop up a tooltip for any recognized address describing its origin (for
example, if it belongs to some thread's stack, the Java heap, a register,
or a memory-mapped region),
* provide the ability to highlight all addresses "near" the selected
address, including registers, threads, and memory-mapped regions.

If there is sufficient interest in creating a public and/or open-source
variant of this internal plugin, I will pitch the idea to my employer. It
shouldn't be too much work to create a public version.

Kind regards,
Maxim.

References:
* https://docs.oracle.com/javase/10/troubleshoot/fatal-error-log.htm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20240411/a66930f8/attachment.htm>