|
Quick Lists
|
|
Bug ID:
|
4298656
|
|
Votes
|
0
|
|
Synopsis
|
stack yellow zone not re-enabled after a StackOverflowError
|
|
Category
|
hotspot:runtime_system
|
|
Reported Against
|
1.3
, 1.0.1
, 1.3.1
, merlin
, kestrel
, 1.3.1_04
, firefly-fcs
, ladybird-rc1
, kestrel-linux
, ladybird-beta
, kest-linux-rc1
, kestrel-solaris
|
|
Release Fixed
|
1.3.1_12,
1.4(merlin-beta) (Bug ID:2030712)
|
|
State
|
11-Closed,
Verified,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4281578
,
4282531
,
4285716
,
4296554
,
4352424
,
4366625
,
4377621
,
4377163
,
4381856
,
4402735
,
4424017
,
4525530
,
4736567
,
4736391
,
4925317
|
|
Submit Date
|
10-DEC-1999
|
|
Description
|
Problem is that the stack yellow zone is disabled on the first occurrence
of a stack overflow for a thread, but never re-enabled after the
StackOverflowError is thrown. The next stack overflow thus enters the
red zone, which the vm treats as fatal. The attached simple java program
so2.java demonstrates this.
|
|
Work Around
|
N/A
|
|
Evaluation
|
xxxxx@xxxxx 2000-12-14
During handling of the 1st overflow, the yellow_zone is disabled via a
call to JavaThread::disable_stack_yellow_zone()
(at src/os_cpu/solaris_sparc/vm/os_solaris_sparc.cpp, line 760).
Need to reenable the guard pages while unwinding the stack during exception
processing.
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
