hs_err_pid file summary proposal
coleen.phillimore at oracle.com
Mon Jul 13 22:39:55 UTC 2015
Mikael tells me I can edit out the '\n', which I will do.
On 7/13/15 6:29 PM, Coleen Phillimore wrote:
> Hi Vladimir,
> Sustaining wanted to know the date of the crash and elapsed time. I
> would have put them all on one line but the function that prints
> 'date' adds a new line. Do you know of another function this could call?
> st->print("time: %s", ctime(&tloc)); // ctime adds newline.
> Thanks for reading and commenting.
> On 7/13/15 5: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
>>> 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