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.
Hu-um ! It's the first time that I see and that I enter an "issue", hopefully - in the right component : debuggercore , - understanding and executing the short advice of Melongo Annabel, the right way. I first posted this issue as a "new topic" in the forum : http://forums.netbeans.org/viewtopic.php?p=32906#32906 . A very usefull debugging functionnality (that is available in some IDE-emulators for micro-controller code): The debugging tool begins first to run without stopping at the mentionned breakpoints, until ... - the values in a set of properties is matching all the values of a predetermined set or - one of the values of a set of properties has reach or is greater (lower) than the respective property in a predefined set. Then, the debugging tool behaves basically : stopping at each breakpoint. Example of use case : I had a very big ArrayList[][][][][][][], filled in dynamically (new Object[]{}) and having an index property for each of the 7 dimensions. Total number of array elements : 1452 ! The process crashed anywhere (ArrayExceptionOutOfBBound). I had to loop 1109 times to find where the bug was located (Not at the first trial, of course). Also interesting with not related properties from any classes of a complex application. Please, vote for this basic debugging feature.
There is a possibility to set a condition on breakpoints. This is likely what you're looking for. When you right-click on a breakpoint icon in the editor gutter, Choose Breakpoint -> Properties and set a desired condition when you need the breakpoint to be hit.