RFR: 8284274: Error reporting crashes because missing ResourceMarks [v2]

[Thomas Stuefe]

On Tue, 12 Apr 2022 19:34:53 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

>> test/hotspot/jtreg/runtime/ErrorHandling/ResourceMarkTest.java line 64:
>> 
>>> 62:     output_detail.shouldMatch("#.+SIGFPE.*");
>>> 63:     output_detail.shouldMatch("This is a message with no ResourceMark");
>>> 64: 
>> 
>> Note that we introduced -XX:+ErrorFileToStdout and -XX:+ErrorFileToStderr, you could use that instead of looking for the hs-err file, and parse output_detail directly for the strings in question. The ErrorHandler tests are older than those switches and could be rewritten too.
>
> Ha Thomas, I copied your test almost verbatim.  If I send all the hs_err file to stdout, jtreg might truncate it and that won't help, also if the test someday fails, the output will be lost in the jtreg truncation.  Having two test do sort of the same thing seemed nice to me.

You are right, truncation could be an issue when analyzing test errors.

-------------

PR: https://git.openjdk.java.net/jdk/pull/8201