RFR: 8276184: Exclude lambda proxy class from the CDS archive if its caller class is excluded [v4]

Calvin Cheung ccheung at openjdk.java.net
Tue Nov 9 19:56:14 UTC 2021


On Tue, 9 Nov 2021 03:09:39 GMT, Ioi Lam <iklam at openjdk.org> wrote:

>> Not in this case. When the `do_entry()` of `ExcludeDumpTimeSharedClasses` is called, it doesn't know that the lambda proxy is associated with a signed `caller_ik`. If there's a need for a log message, it needs to be added in the `do_entry()` of `CleanupDumpTimeLambdaProxyClassTable`.
>
> Checking the exclusion message, even if it's printed, will be more involved, especially if you want to ensure that several such proxy classes are excluded. Since the proxies have similar but non-deterministic names (they have numbers in them), you will need to search for a pattern in the log and count the number of times it appears.
> 
> I think it's easier and more reliable to run with `-Xlog:cds+class=debug`, and check that the proxy class is not in the print out.

There's a bug in Hello.java which I've fixed in my latest push.
Also updated SignedJar.java to perform more checks on the output.

-------------

PR: https://git.openjdk.java.net/jdk/pull/6205


More information about the hotspot-runtime-dev mailing list