We have some 'at runtime' checks for availability of SetSecurityDescriptorControl in the Windows perfmemory coding. But those were done for very old Windows versions like Win98 and can probably be removed.
Looking at the description
https://learn.microsoft.com/en-us/windows/win32/api/securitybaseapi/nf-securitybaseapi-setsecuritydescriptorcontrol
it is available at least since Win2003/XP so the function can be called directly.
Looking at the description
https://learn.microsoft.com/en-us/windows/win32/api/securitybaseapi/nf-securitybaseapi-setsecuritydescriptorcontrol
it is available at least since Win2003/XP so the function can be called directly.
- relates to
-
JDK-8368781 PerfMemory - make issues more transparent
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/b597b655
-
Review(master)
openjdk/jdk/27937