|
Quick Lists
|
|
Bug ID:
|
4402735
|
|
Votes
|
3
|
|
Synopsis
|
[server] stack yellow zone not re-enabled after a StackOverflowError
|
|
Category
|
hotspot:runtime_system
|
|
Reported Against
|
2.0
, 2.0_fcs
, 2.0_rc1
, 1.3.1_11
, 2.0_beta
, merlin-beta
, kest-sol-rc1
, ladybird-beta
|
|
Release Fixed
|
1.3.1_12,
1.4(merlin-beta) (Bug ID:2039653)
|
|
State
|
11-Closed,
Verified,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4298656
,
4302287
,
4302289
,
4396960
,
4400369
,
4427144
,
4736391
,
6225936
|
|
Submit Date
|
08-JAN-2001
|
|
Description
|
This is a placeholder for the repeated stackoverflow fixes for the server
compiler. The interpreter and client compiler changes were fixed under bug
4298656.
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 2001-03-19
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
|
|
|
|
