[master] Integrated: OMWorld: Fix javaVFrame::print_lock_info_on
Axel Boldt-Christmas
aboldtch at openjdk.org
Tue Apr 23 06:11:45 UTC 2024
On Mon, 22 Apr 2024 12:30:24 GMT, Axel Boldt-Christmas <aboldtch at openjdk.org> wrote:
> OMWorld: `Fix javaVFrame::print_lock_info_on` printing. If the ObjectMonitor is `nullptr` and the header is `has_monitor` then we must be in the process of locking. (We cannot have locked, as that would have prevented deflation).
>
> This commit is currently based on ffc4c2fd5ba1c28432a5d5e84b8ada95fba7eeb8 without a merge. So GHA is not tested with lilliput. As long as this is mergable without conflicts (and no manual merge is performed) it will also be possible to move this commit down below lilliput on-top of OMWorld directly.
This pull request has now been integrated.
Changeset: 8e25cd67
Author: Axel Boldt-Christmas <aboldtch at openjdk.org>
URL: https://git.openjdk.org/lilliput/commit/8e25cd67307e84ba1ffd0b404d906c2f04e67ea2
Stats: 4 lines in 1 file changed: 2 ins; 1 del; 1 mod
OMWorld: Fix javaVFrame::print_lock_info_on
Reviewed-by: rkennke
-------------
PR: https://git.openjdk.org/lilliput/pull/158
More information about the lilliput-dev
mailing list