JDK-6782740 : JVM crash after fixing classes through debugger
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: hs11,5.0u14,6u2,7u4
  • Priority: P4
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • OS: generic,linux,linux_ubuntu
  • CPU: generic,x86
  • Submitted: 2008-12-09
  • Updated: 2023-12-13
  • Resolved: 2015-04-09
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
tbdResolved
Related Reports
Duplicate :  
Duplicate :  
Description
See http://www.netbeans.org/issues/show_bug.cgi?id=152648 for exact steps ho to reproduce this:

-open project stored in 
http://qa.netbeans.org/modules/debugger/promo-h/MemoryView.zip
-Toggle line breakpoint on line 25 of the file FixAndContinue.java 
-Invoke Debug File action form context menu of file FixAndContinue.java in Projects view 
-Invoke Step Into until debugger stops on line 26 
-Insert line before line 30 with code System.out.println("Added line"); 
-Change method call on line 31 to afterFix(); 
-Invoke Apply Code Changes 
-Invoke Step Into until end of application
when reaching line 30 an error message is thrown:
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x061c372a, pid=7714, tid=3084200848
#
# Java VM: Java HotSpot(TM) Client VM (11.0-b15 mixed mode linux-x86)
# Problematic frame:
# V  [libjvm.so+0x1c372a]
#
# An error report file with more information is saved as:
# /home/tester/NetBeansProjects/MemoryView/hs_err_pid7714.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Java Result: 134
BTW: it might be a hotspot issue, but I did not find the hotspot category in this mess.

Comments
PUBLIC COMMENTS It's possible that #6742507 is not really a duplicate of this, therefore #6742507 needs to be verified/reopened after this is fixed.
28-04-2011