There is a regression in JDK 23, but I cannot attach a jar at bugreport.java.com.

[Asva Raten]

Thanks for replying.

I forgot to mention, there is no way to specify the issue subcomponent as "jdeps" on the bugreport website. The issue actually seems to be with the new in preview Classfile API, which is used by jdeps in JDK 23 (the exception occurs in signature parsing), but there is no way to specify that either.

Under which subcomponent am I supposed to file this report?

The process to generate the jar for reproduction includes third-party software that needs to be downloaded and executed (proguard), is that okay? It becomes pretty complex and needs configuration as well and I fear that might discourage the bug report handlers. I thought just sending a jar would be easier, as it can be easily compared between jdeps of JDK 22 and jdeps of JDK 23. But if you want to I can write all the instructions to do it, the instructions would be for with the build tool that I use.

P.S. I sent this email again because the first one went to the wrong place.




________________________________
From: discuss <discuss-retn at openjdk.org> on behalf of mandy.chung at oracle.com <mandy.chung at oracle.com>
Sent: Friday, October 4, 2024 7:12 PM
To: discuss at openjdk.org <discuss at openjdk.org>
Subject: Re: There is a regression in JDK 23, but I cannot attach a jar at bugreport.java.com.



On 10/4/24 8:01 AM, Asva Raten wrote:
I have a jar file that jdeps in JDK 22 can properly analyze and return correct results for, while jdeps in JDK 23 crashes for the exact same jar file. Now I don't know, there might be an issue with the jar file itself but since jdeps in JDK 22 can analyze it while jdeps in JDK 23 cannot, there is a change of behavior that I want to report. Maybe it is the new JDK's behavior that is incorrect in which case it should be fixed, or if it is correct then that should be documented in the release notes because it breaks backward compatibility.

I was writing a report at bugreport.java.com, but there is no way to attach a jar file on there. The jar in question is an uber/fat/shaded jar that has been processed by an optimization tool, Proguard, so I don't want to inconvenience the JDK team with all the steps of making a fat jar with the library and running Proguard on it. I need to just attach a jar file for them to be able to debug it using jdeps.

What should I do?


Submitting the issue to bugreport.java.com  is the right way to do it.   Please include the steps of reproducing the issue that can help understanding what are involved.   The submitter will be contacted if we need more information or any files we may need.

Mandy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20241004/a5370513/attachment.htm>