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.
I have Maven projects which are built with "mvn clean install". I also have "Generate debugging info" checked in the projects properties. However, in some classes I get the above message when trying to set up a breakpoint, but in some the breakpoints can be set without problems.
Then it should be analyzed why the compiler does not include the line number information into the class files in the Maven project. Are you sure that the affected classes are not from some library that could be compiled without debugging info?
It can be easily verified that the debuggin info is present in the class files via: javap -l <class file>
The following is the result of javap -l on the class and method I am interested in; ... protected boolean nextLevel(java.sql.ResultSet) throws java.sql.SQLException; LineNumberTable: line 174: 0 line 176: 19 line 177: 46 line 178: 60 line 180: 62 line 185: 64 line 187: 66 line 188: 74 line 190: 107 line 191: 117 line 192: 128 line 194: 131 line 197: 155 line 199: 188 line 201: 230 line 202: 232 line 206: 238 line 208: 247 LocalVariableTable: Start Length Slot Name Signature 117 11 6 value Ljava/lang/String; 107 21 5 field Ljava/lang/String; 85 46 4 i$ Ljava/util/Iterator; 188 47 5 field Ljava/lang/String; 166 72 4 i$ Ljava/util/Iterator; 0 249 0 this Lcom/snapon/sbs/capps/core/data/TwoLevelResultSetHandler; 0 249 1 rs Ljava/sql/ResultSet; 66 183 2 newObjectFound Z 74 175 3 currentObjects Ljava/util/Map; ... However, NetBeans still does not allow me to create a breakpoint on line 174 here.
... Not able to submit breakpoint LineBreakpoint ... ... reason: No executable location available at line 174 ...
Thanks for the info. The LineNumberTable is there, therefore debugger should be able to submit breakpoints. Is it possible to provide some sample project so that we can test it and locate the bug? Please include the compiled classes as well. Thanks.
Unfortunately I am not working on this project anymore (I changed client) and don't have access to the code. If there is anybody out there with similar problems, please submit sample code.
Unfortunately, this is the only report that we got about this problem. Therefore resolving as incomplete, please reopen if you encounter the problem in the future again and include some sample project with the class files.