RFR: JDK-8292351: tty should always live
Thomas Stuefe
stuefe at openjdk.org
Mon Aug 15 09:43:22 UTC 2022
The default stream object tty is used in many places but its lifetime is limited. It gets born not-quite at the beginning of VM initialization and dies in DestroyVM. This leaves time windows before VM initialization and after VM cleanup where logging to tty crashes.
This has been bugging me in the past, especially when wanting to use tty in code that runs very early (NMT preinit system, for example), and also causes problems for code that runs post-cleanup. Mostly this affects logging and error logging.
tty should always be safe to write to, and that is trivial to do.
-------------
Commit messages:
- JDK-8292351-tty-should-always-live
Changes: https://git.openjdk.org/jdk/pull/9874/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=9874&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8292351
Stats: 8 lines in 1 file changed: 6 ins; 0 del; 2 mod
Patch: https://git.openjdk.org/jdk/pull/9874.diff
Fetch: git fetch https://git.openjdk.org/jdk pull/9874/head:pull/9874
PR: https://git.openjdk.org/jdk/pull/9874
More information about the hotspot-dev
mailing list