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 145676 - Step into doesn't warn about uncompilable source
Summary: Step into doesn't warn about uncompilable source
Status: VERIFIED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: Macintosh All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-30 11:45 UTC by Peter Pis
Modified: 2008-09-12 15:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Pis 2008-08-30 11:45:27 UTC 
Product Version: NetBeans IDE Dev (Build 200808300201)
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-121
System: Mac OS X version 10.4.11 running on ppc; MacRoman; en_US (nb)
Userdir: /netbeans/65/user

See issue #144111 for attached files.
Steps:
1. Put the bkpt on line where "Thread.sleep" is being called.
2. After bkpt is hit proceed by stepping into the code of "number" method.
3. Watch "Debugger Console" - when "Debugger stopped on uncompilable source code." is printed, correct the code (e.g.
"return 1;"), 
4. Current thread pops out of the method.
5. Push F7 and break the code (retrun ;) and save the file. 
6. Thread pops out.

Now push F7 several times - it never print "Debugger stopped on uncompilable source code." in "Debugger Console". And finally thread quits.
Comment 1 Martin Entlicher 2008-09-09 12:56:44 UTC 
I have a similar experience from other case as well. It looks like the RuntimeException that is thrown on uncompilable
code is not caught on subsequent occurrence.
Comment 2 Martin Entlicher 2008-09-09 17:16:39 UTC 
It looks like a JDI defect again. I have no proof yet, I'm going to write some testcase.
Resetting TM to TBD, since this is not evaluated yet, a NetBeans-independent test-case is necessary to find out where
the problem is.
Comment 3 Martin Entlicher 2008-09-10 13:16:00 UTC 
Yes, it is a defect of Sun's JDK. This can not be fixed in NetBeans.
See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6746746
Comment 4 Peter Pis 2008-09-12 15:05:49 UTC 
Verified wontfix.