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.
[#200402221900, jdk1.5.0] 1st message: Thread xxx stoped at Srv.java:80 2nd message: Break point hit at line 35 in class .... Please fix it asap, it cuses automated tests random fails. The evil is the random messages order. If I can choose I would prefer to produce 1st message as second.
This can hardly be a P2. You can check this situation even in tests. Just read both messages.
From user point of view I agree it is P4. But due to this problem debugger tests are not stable and cannot run on daily basis. Thus debugger is not tested automatically in daily builds. Hanzi, it is not possible to wait for two messages. Currently in UI tests you can wait for a specific message, which is on the last line. This makes no problems for other tests, so I doubt somebody will enhance the functionality just because debugger does not behave deterministic.
I do not want to do not trivial change in our production code only because of you do not want to do not trivial change in your tests. We are in stabilization phase. This bug is p4 from user point of view, and we have some other bugs too.
No chance to fix it in 4.1.
The problem is still there: User program running Breakpoint hit at line 30 in class debuggertest1.TestSmartStep by thread main. Thread main stopped at TestSmartStep.java:30. Breakpoint hit at line 43 in class debuggertest1.TestSmartStep by thread main. User program running Thread main stopped at TestSmartStep.java:43. User program running Thread main stopped at TestSmartStep.java:54. This must be a (missing) synchronization issue... But it looks that "Thread main stopped at ..." is always printed as the last message now.
This is a dupl. of issue #50811. *** This issue has been marked as a duplicate of 50811 ***
Verifying in development build #200607181800 of NetBeans 6.0.