This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 152648

Summary: Apply code changes not working correctly
Product: debugger Reporter: matusdekanek <matusdekanek>
Component: JavaAssignee: issues@debugger <issues>
Status: CLOSED WONTFIX    
Severity: blocker CC: pjiricka
Priority: P3    
Version: 6.x   
Hardware: All   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: simple java file. this file did not throw error (although it does similar task as the one errorneous)
messages.log
mesages.log after closin IDE (previous one might be invalid for this issue)
error log

Description matusdekanek 2008-11-07 10:27:50 UTC
adding a new line to code and applying change results in debug stop (and starts debug of another project file)

steps to reproduce
-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
debug of FixAndConstinue ends and starts debug of MemoryView.java

This behaviour was not observed in another file, with which I tried to reconstruct this bahaviour. I will post it here.

Although it may not be isssue for debugger(or even for netbeans), I post it here, since program normally does work and 
I think it really might have something to do with debugger.

System:
Product Version: NetBeans IDE Dev (Build 200811070201)
Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15
System: Linux version 2.6.24-21-generic running on i386; UTF-8; en_US (nb)
Comment 1 matusdekanek 2008-11-07 10:29:27 UTC
Created attachment 73447 [details]
simple java file. this file did not throw error (although it does similar task as the one errorneous)
Comment 2 matusdekanek 2008-11-07 10:30:11 UTC
Created attachment 73449 [details]
messages.log
Comment 3 matusdekanek 2008-11-07 10:32:54 UTC
Created attachment 73450 [details]
mesages.log after closin IDE (previous one might be invalid for this issue)
Comment 4 matusdekanek 2008-11-07 10:34:49 UTC
Created attachment 73451 [details]
error log
Comment 5 Martin Entlicher 2008-12-09 14:21:31 UTC
100% reproducible for me.
A bug in JVM.
The strange thing is, that it can be reproduced only for the first time. Second attempt to follow the same steps finish
successfully.
Can not be fixed in NetBeans, of course.
Comment 6 Martin Entlicher 2008-12-09 14:37:54 UTC
I've submitted this for JDK at http://bugs.sun.com/view_bug.do?bug_id=6782740
Comment 7 Quality Engineering 2010-04-29 09:45:17 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.