Thank you Erik, much appreciated
Sent from Outlook for Mac From: Erik Joelsson <[email protected]> Date: Friday, 2 January 2026 at 14:34 To: Andrew Leonard <[email protected]>, [email protected] <[email protected]> Subject: [EXTERNAL] Re: RFR: 8351842: Windows specific issues in combination of JEP 493 and --with-external-symbols-in-bundles=public - Full symbols location?? This Message Is From an External Sender This message came from outside your organization. Report Suspicious<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/AdhS1Rd-!99FRGPyyUiXxv7bTLuQqsvS4MGXLa9HzRskApa_-B9he7KLigAVp-kzS8r4TewQkpqab0byXLQ1DqR3-7e5YOIbzVeevK37L_hizFA$> On 1/2/26 03:57, Andrew Leonard wrote: Hi, I’m looking to understand the situation on the production of full debug symbols, as we’ve noticed at Adoptium jdk26 JDK images no longer have the full debug symbols where they used to be in the JDK image? For Temurin release builds we use external symbols (--with-debug-level=release --with-native-debug-symbols=external) and then move the JDK debug info files to a separate debug image tarball, I’m trying to figure what we need to change? Are the images/symbols folder files full debug files? Should we get them from there instead? Thanks Yes, that is correct. The debug symbols are now only put into the symbols image, unless you explicitly configure your build to include them in the regular image and bundles using `--with-external-symbols-in-bundles=full`. I would also recommend looking at the `make bundles` or `make product-bundles` targets as those will generate the appropriate bundles for you, though on Windows they are zip bundles as that's a more commonly used packaging format for that platform. /Erik Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
