hs_err_pid file summary proposal
Daniel D. Daugherty
daniel.daugherty at oracle.com
Mon Jul 13 22:05:22 UTC 2015
time: Mon Jul 13 22:56:17 2015
is useful for correlating against system logs on the
test machine... Things like transient "NFS server not
responding" or "out of the diskspace" or...
On 7/13/15 3:59 PM, Vladimir Ivanov wrote:
> I'm curious how important is it to have 3 lines of time info:
> time: Mon Jul 13 22:56:17 2015
> timezone: DFT
> elapsed time: 13 seconds (0d 0h 0m 13s)
> IMO elapsed time is the one deserving mentioning in the summary.
> Best regards,
> Vladimir Ivanov
> On 7/11/15 1:31 AM, Coleen Phillimore wrote:
>> I've been working on improvements to the hs_err_pid file. One
>> suggestion was to add a summary because some information is hard to find
>> in the file, and is very helpful during triaging. Realizing that
>> everyone has their own opinion of the most important information in the
>> hs_err_pid file, the summary information is minimal and additive, and
>> represents the information that we generally add to the bug report to
>> supplement the hs_err_pid file. Also the stack traces have been moved up
>> because that's what my opinion of the most important thing is.
>> This summary proposal can be found in my last 2 comments in bug:
>> There are some samples in the bug report als.
>> Please reply with comments. I have implemented this, but this is not an
>> RFR yet.
>> open webrev at http://cr.openjdk.java.net/~coleenp/8026324.01/
More information about the hotspot-dev