RFR: 8048190: NoClassDefFoundError omits original ExceptionInInitializerError [v2]

Coleen Phillimore coleenp at openjdk.java.net
Thu Aug 5 18:30:32 UTC 2021


On Thu, 5 Aug 2021 13:10:45 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

>> Yes, regarding your other comment about whether the original exception should be reloaded and reinitialized, and whether its initialization could be the cause of the original exception.  I'll try to find a creative solution here so that the most common cases are still supported because I think this would be a helpful feature most of the time.  If you have some ideas, let me know (either here or offline).  Thanks.
>
> I wonder if I can use a predefined exception like ExceptionInInitializerError and put the original exception in with the message?

You're right.  new_exception does surprising things.  If it gets an exception during the call, it returns a handle to that exception, which is not what I want at all.  I'll return null in that case.

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

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


More information about the hotspot-dev mailing list