RFO: a tool to analyze HotSpot fatal error logs

[Maxim Kartashev]

> Does the tool  work  both with  hserr files (“HotSpot fatal error logs”)
   and also   the  output  of   jcmd  <pid>  VM.info   ?

Yes since the latter is more or less a short version of the former.

> How well can it handle incomplete hserr files  (we sometimes see those in
case of bad crashes) ?

As well as can be expected; some of the crashes are naturally redacted
because of induced crashes and we're taking whatever information is there.
We're also processing crashes from many JVM versions each of which
introduces its own variance to the content and format of the log.

There are many heuristics in the parsing so it can yield incorrect results
(rarely), but it also makes parsing quite stable in the sense that
practically any log a human can read the tool can also read.

> 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) ?

You can go to the declaration of the PasswordAuthentication class when
looking at things like
Event: 112.303 loading class java/net/PasswordAuthentication

I haven't thought of opening source files via links from the log itself
since I rarely see them there (mostly assertion failures), but it's easy
enough to implement.

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

I think this is the story for many on the list. I've seen enough people on
youtube turning to ad hoc scripts to make sense of addresses in the logs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20240412/ef465df2/attachment.htm>