|
Quick Lists
|
|
Bug ID:
|
6503017
|
|
Votes
|
0
|
|
Synopsis
|
assert(fr().is_deoptimized_frame(),"frame must be scheduled for deoptimization")
|
|
Category
|
hotspot:compiler2
|
|
Reported Against
|
|
|
Release Fixed
|
hs10(b06),
6u4(b03) (Bug ID:2171894)
, 7(b06) (Bug ID:2176824)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
|
|
Submit Date
|
11-DEC-2006
|
|
Description
|
Nightly test of this test
nsk.jdwp.StackFrame.SetValues.setvalues001
failed after patchless deopt was putback.
Posted Date : 2006-12-11 13:50:44.0
From the putback comment:
This was caused by patchless deopt. Basically when the setvalue code is used
for a compiled frame it deopts it so that the debuggers can see (and set) the
locals in the interpreter frame. The assert fired because the compiled vframe
was the the frame before the deopt occurred. The code actually worked fine but
the assert I put in to be sure that we deopted before trying to set the values
fired. The fix is to re-read the frame after the deopt is scheduled.
Posted Date : 2007-01-17 21:18:50.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
From the putback comment:
This was caused by patchless deopt. Basically when the setvalue code is used
for a compiled frame it deopts it so that the debuggers can see (and set) the
locals in the interpreter frame. The assert fired because the compiled vframe
was the the frame before the deopt occurred. The code actually worked fine but
the assert I put in to be sure that we deopted before trying to set the values
fired. The fix is to re-read the frame after the deopt is scheduled.
Posted Date : 2007-01-17 21:18:50.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
