RFO: a tool to analyze HotSpot fatal error logs

[Baesken, Matthias]

Hello Maxim,  this sounds like an interesting project.
Does the tool  work  both with  hserr files (“HotSpot fatal error logs”)    and also   the  output  of   jcmd  <pid>  VM.info   ?
How well can it handle incomplete hserr files  (we sometimes see those in case of bad crashes) ?
Can the tool  “mix in” / augment   additional information  into the  views of the error log   (like a bit of source code or links into the  stack traces for example) ?

I thought about  creating s similar tool myself in the past, but did not happen so far …

> 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.

Sounds like a great idea !

Best regards, Matthias


Von: hotspot-dev <hotspot-dev-retn at openjdk.org<mailto:hotspot-dev-retn at openjdk.org>> im Auftrag von Maxim Kartashev <maxim.kartashev at jetbrains.com<mailto:maxim.kartashev at jetbrains.com>>
Datum: Donnerstag, 11. April 2024 um 16:06
An: discuss at openjdk.org<mailto:discuss at openjdk.org> <discuss at openjdk.org<mailto:discuss at openjdk.org>>, hotspot-dev at openjdk.org<mailto:hotspot-dev at openjdk.org> <hotspot-dev at openjdk.org<mailto:hotspot-dev at openjdk.org>>
Betreff: RFO: a tool to analyze HotSpot fatal error logs
Sie erhalten nicht oft eine E-Mail von maxim.kartashev at jetbrains.com<mailto:maxim.kartashev at jetbrains.com>. Erfahren Sie, warum dies wichtig ist<https://aka.ms/LearnAboutSenderIdentification>
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/20240412/b8786b8e/attachment-0001.htm>