<div dir="ltr">Thank you, Eric!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 6, 2024 at 7:21 PM <<a href="mailto:erik.joelsson@oracle.com">erik.joelsson@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On 5/6/24 09:26, Thomas Stüfe wrote:<br>
> Hi,<br>
><br>
> is there a way to reliably prevent the jvm from being called with <br>
> -Xshare:dump during build?<br>
><br>
> Often, when I tinker with metaspace or compressed klass pointers, CDS <br>
> gets broken. During development, that is fine; it is a temporary state.<br>
><br>
> However, if -Xshare:dump is invoked, it may crash the JVM and break <br>
> the build.<br>
><br>
> I specified --disable-cds-archives and <br>
> --disable-jvm-feature-link-time-opt. But still, link time optimization <br>
> step runs and calls the build JVM with -Xshare:dump. Is that a bug?<br>
><br>
I think if you add --disable-generate-classlist to that list of <br>
configure arguments, this particular invocation with -Xshare:dump will <br>
go away.<br>
<br>
/Erik<br>
<br>
> Thanks, Thomas<br>
><br>
> P.S. Also, how is this handled for crossbuilds, where generating <br>
> shared archives on the build machine makes little sense?<br>
><br>
><br>
><br>
</blockquote></div>