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.
Created attachment 131480 [details] Screen print Build 201301300001 The debugger breaks on lines that have breakpoints but the breakpoint marker is not shown in the source file. The breakpoints have shown before, and they belong to files that weren't changed. The breakpoints window shows them. This is very confusing, especially in combination with bug 225301.
Product Version: NetBeans IDE 7.3 (Build 201302062200) Java: 1.7.0_11; Java HotSpot(TM) Client VM 23.6-b04 Runtime: Java(TM) SE Runtime Environment 1.7.0_11-b21 System: Linux version 3.0.0-12-generic running on i386; UTF-8; cs_CZ (nb) User directory: /home/cesilko/.netbeans/7.3 Cache directory: /home/cesilko/.cache/netbeans/7.3 For the record I cannot reproduce it even with not shown line numbers.
I see this in - library jar files - first rate project files This time, I could definitely eliminate as possible cause multiple versions of the same file - project file. The java file was not opened before the debugger stopped on a breakpoint. The java file has 7 breakpoints in the breakpoints window but none is shown in the editor. The file org-netbeans-modules-debugger-Settings.properties has 2 duplicate identical entries for the breakpoint that was hit. If I toggle the breakpoint in the editor then first nothing happens whcih is consistent. Only when clicking the seond time, a breakpoint is shown in the editor. But the other breakpoints are still not shown. So quite clearly, the debugger fails to display the breakpoints where it should according to conditions.
Created attachment 131765 [details] breakpoints properties file
The duplicate entries are .25 and .27
Unfortunately, it's hard to find out, why something does not happen. Can you also attach messages.log file so that we can see if there are some exception, which could break something?
Created attachment 131855 [details] logs in zip file
Thanks for the log fies. This is likely the reason, why you do not see breakpoints in editor: java.lang.NullPointerException: null AnnotationType for:org-netbeans-modules-j2ee-sunserver
Created attachment 132487 [details] log file after new instance of the issue I have an instance of the issue now where the suspect log entry is different: INFO [org.glassfish.tools.ide]: Caught InterruptedIOException: null Please ignore the exception at the top, org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. That was due to a missing domain.xml after a power loss which I fixed.
Created attachment 133731 [details] log file from another instance
*** Bug 227646 has been marked as a duplicate of this bug. ***
Created attachment 133953 [details] Screen print without errors in log
Created attachment 133954 [details] log file without errors I have a case where the log does not contain any exceptions. That means we can assume that any exceptions in the log cannot be blamed. What else can be done to identify the root cause of this?