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.
Summary: | Exception occured in beta 5 (not in beta4) during saving | ||
---|---|---|---|
Product: | debugger | Reporter: | Andreas Schoerk <aschoerk> |
Component: | Code | Assignee: | Marian Petras <mpetras> |
Status: | CLOSED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Andreas Schoerk
2001-11-26 16:55:18 UTC
So, there is no editor in stack trace, and the first from top is debugger, so passing to debugger. Target milestone -> 3.3.1. Fixed in branch 'release33' and in the main trunk. I was not able to reproduce it but I believe it has happened. I have made a fix which should prevent the exception. It still may write a short warning into a log file in some cases but it does not affect functionality. If this bug is really fixed, there should not be any "short warning ". So fix it, please or do not write anything to a log file . Fixed in branch 'release33'. Fixed also in the main trunk. The exception is thrown if method 'dispose()' is called multiple times on a single breakpoint. Multiple calls did not cause any problems until class 'BreakpointUpdater' was added. Method 'BreakpointUpdater.dispose()' expected that it is called just once per a single breakpoint. A fix integrated into the main trunk and to branch 'release33' assures both that 'dispose()' is called just once plus it makes 'BreakpointUpdater.dispose()' resistant to multiple calls. Fixed also in branch 'release330'. |