JDK-8042155 : [TESTBUG] Tests for stack guard pages have to be cleaned up
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: linux
  • CPU: generic
  • Submitted: 2014-04-29
  • Updated: 2014-06-26
  • Resolved: 2014-05-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b17Fixed
Related Reports
Duplicate :  
JDK-8042011 - [TESTBUG] runtime/6929067/Test6929067.sh segfaulted on Linux i586 in RT_Baseline
Relates :  
JDK-8029139 - [TESTBUG] runtime/InitialThreadOverflow/testme.sh fails with exit code 127
Relates :  
JDK-6929067 - Stack guard pages should be removed when thread is detached
Description
Tests for 6929067 and 8009062 should be composed to single test that provide better testing for stack guard pages behaviour
Comments
Furhter investigation shows it's a test issue, not the hotspot one. Changing synopsys and description accrodingly.
01-05-2014
I don't see how JavaThread::remove_stack_guard_pages can operate on a different native thread. Are the main thread and separate thread identities somehow getting conflated? Do the two threads somehow share the same stack region?
01-05-2014
When jvm->DetachCurrentThread and subsequent call to JavaThread::exit() calls remove_stack_guard_page it removes stack guard page from the initila thread stack despite the fact, we create a separate thread and call DetachCurrentThread from it.
30-04-2014
I don't understand the description - how can detach _current_ thread affect anything but the current thread ???
30-04-2014