NB trunk build 200407131800, JDK1.4.2_05, Solaris 9.

Sometimes, the debugger does not stop on line
breakpoints (it starts to ignore all line
breakpoints).

This problem happens randomly.

I am attaching a trivial application on which I am
sometimes able to reproduce the problem.

I am also attaching two logs from the console and
the debugger console, one represents correct
debugging, one represents the case where the
breakpoints were ignored. The steps used were the
same in both cases:
1.Download, unpack, and open provided test
project. Open javaaplication1.Main.
2. Add line breakpoints at lines 25 and 28.
3. Start debugger via "Run/Run Other/Debug".
4. After the debugger stops at the first
breakpoint, do twice step over, step over (now the
debugger should stay on the second breakpoint, but
if the problem occurs, in the debugger console the
following line is missing "Breakpoint reached at
line 28 in class javaapplication1.Main by thread
main.")
5. Do Continue (via shortcut Ctrl-F5) so long that
the debugging finishes. If the problem occurs,
after pressing Ctrl-F5 once, the debugger does not
stop on the breakpoint at line 28 and the
application is runned without stopping until it
finishes.

The command line options used to get the console
logs were: -J-Dnetbeans.debugger.breakpoints=true
-J-Dnetbeans.debugger.jdievents=true

Reproducibility info: it seems that the
probability of this problem is much higher for
more complicated applications/projects. Also
switching between "internal" and remote debugging
seems to make the probability higher.