On Feb 14, 2018, at 12:06 PM, Daniel Heidinga <daniel_heidi...@ca.ibm.com>
> The stackoverflow in this example occurs in the static argument resolution
> phase, not the BSM invocation.
In one particular JVM implementation with which I am familiar,
an OS stack overflow occurred in the static argument resolution
phase of a test case like this, *but* it was not converted into
a Java SOE; it turned into a hard crash.
This was fixed, in that JVM implementation, by threading the
static argument resolution logic through a Java call, which
brought the appropriate overflow sensing and conversion