hs_err files in docker containers generated by our jtreg tests

[Baesken, Matthias]

Hello, we have a couple of jtreg tests  starting java processes not directly on the test host,  but  in docker containers     ( e.g.   containers/docker/    tests ) .
In case those processes crash we get something like this  :

PrintContainerInfo: Entering
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x00007fffb021fc50, pid=1, tid=7
#
# JRE version: OpenJDK Runtime Environment (23.0) (fastdebug build 23-internal-adhoc.jenkinsi.jdk)
# Java VM: OpenJDK 64-Bit Server VM (fastdebug 23-internal-adhoc.jenkinsi.jdk, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-ppc64le)
# Problematic frame:
# C  [libz.so.1+0xfc50]  inflateReset+0x60
#
# Core dump will be written. Default location: //core.1
#
# An error report file with more information is saved as:
# //hs_err_pid1.log


Unfortunately the hserr file  ist not there any more for easy inspection  after the jtreg run  (and not all  crashes are nicely reproducable) .
Should we somehow  collect the hs_err and  bring it to the host ?

Or simply set   (for the docker/container related tests)   -XX:+ErrorFileToStderr   to  get the  error-output to stderr instead  (makes life easier for those tests )  ?



Best regards, Matthias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/container-discuss/attachments/20240214/66e388fd/attachment-0001.htm>