Crash due to stack overflow situation if new frame is interpreted and previous is compiled

[Coleen Phillimore - Sun Microsystems]

I remember that bug.  The idea was to stack bang Shadow Pages before we 
put the interpreter frames back on the stack but it didn't work, or 
probably wasn't coded carefully enough.  The calculations of how much 
stack to check was probably wrong.

Coleen

On 02/09/10 18:32, Vladimir Kozlov wrote:
> It could be another incarnation of next bug (in Fix Failed state):
>
> 6474998: nsk/regression/b4688375 test crashes hotspot
>
> Vladimir
>
> Christian Thalinger wrote:
>> On 02/ 9/10 05:12 PM, Hollich, Volker wrote:
>>> Hello everyone,
>>>
>>> I observed that the current hotspot (both client/server) fails if a
>>> stack overflow situation occurs while generating an interpreted frame
>>> on top of a compiled frame. The small example program enclosed fills
>>> the stack with compiled frames and makes sure the interpreted frame
>>> does not fit onto the stack. In order to provoke this situation, I
>>> created a method with extraordinary many locals but this is no
>>> prerequisite for the crash situation per se. I see the test crashing
>>> hotspots on sparc, x86_32, and x86_64. Given the -Xint option, the
>>> test passes easily. The enclosed jar file is runnable and contains
>>> the java source code as well.
>>
>> I filed:
>>
>> 6924814: Crash due to stack overflow situation if new frame is
>> interpreted and previous is compiled
>>
>> -- Christian