Review request: flush the output streams before OnError commands

[Chuck Rasbold]

Thanks for looking at this.

I'll admit I originally overlooked SuppressFatalErrorMessage, and I'm not
familiar with conventional use of the option.

After looking at it, the intent of that flag seems to be to avoid all post
fatal error processing. See bug
6194668<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6194668>.
 Under that description, I would argue that flushing the streams is
post-error processing, and my changes are in keeping with that.

If you don't agree with me, do you think calling ostream_abort() before
os::abort() is the right thing to do?

My last preference would be to leave the calls in the OS specific shutdown
routines.

-- Chuck

On Wed, Sep 15, 2010 at 11:38 AM, Vladimir Kozlov <
vladimir.kozlov at oracle.com> wrote:

> When -XX:+SuppressFatalErrorMessage the log files will not be flushed.
>
> Vladimir
>
> Chuck Rasbold wrote:
>
>> I've found the LogCompilation files incomplete when a JIT crashes and
>> OnError is used to move the files.
>>
>> http://cr.openjdk.java.net/~rasbold/OnError/webrev.00
>>
>> NoBugId: Contributed-by: rasbold at google.com <mailto:rasbold at google.com>
>>
>>
>> When the VM aborts, flush the output streams before OnError commands are
>> processed.
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20100915/7f98bd20/attachment.html