JDK-2137150 : JVM abort with Full thread dump by kill -QUIT
  • Type: Backport
  • Backport of: JDK-6300358
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2006-04-14
  • Updated: 2014-02-27
  • Resolved: 2006-05-11
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.
Other JDK 6
1.4.2_13Fixed 6 b84Fixed
Comments
SUGGESTED FIX As a temporary fix pending the resolution of 6412693, get_thread_name should never return NULL. Given the circumstances in which it can return null it is suggested that it instead return "<no-name - attaching>"
18-04-2006
EVALUATION The Thread::get_thread_name() method is used in many contexts where it is assumed that NULL can never be returned for a thread name. Due to the way native threads attach to the VM through JNI (see 6412693) this is not the case. If NULL is encountered then it will cause a segmentation fault.
18-04-2006