On Tue, 4 Jun 2024 17:25:04 GMT, Leonid Mesnik <lmes...@openjdk.org> wrote:
> The kill sends async exception that is thrown somewhere during > log.display(...) method. > The log shows that it is thrown while PrintStream locking moving it into an > inconsistent state. > So the fix is to use some method that could be safely interrupted by async > exception. test/hotspot/jtreg/vmTestbase/nsk/jdb/kill/kill001/kill001a.java line 153: > 151: } > 152: } > 153: Have you tried an empty method? I don't think it's a matter of how much time you spend in the method, but just whether or not a JVM async exception polling point is reached. I suspect the method call or return will be a polling point, but I'm unsure what happens if the method call is elided by the JIT because it does nothing. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/19547#discussion_r1626486192
