P4
Martin Buchholz comments:
I was also frustrated that a StackOverflowError failed to report the name of the thread and the stack size that was exceeded. But -Xlog:threads*=trace helped there.
David Holmes responds:
The issue there is that SOE instances are allocated natively without executing any Java code (as we have run out of the Java stack) so we can't (easily) create a String message for the exception. However -Xlog:exceptions could be expanded to report that information at the point we throw the SOE.
I was also frustrated that a StackOverflowError failed to report the name of the thread and the stack size that was exceeded. But -Xlog:threads*=trace helped there.
David Holmes responds:
The issue there is that SOE instances are allocated natively without executing any Java code (as we have run out of the Java stack) so we can't (easily) create a String message for the exception. However -Xlog:exceptions could be expanded to report that information at the point we throw the SOE.