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.

Bug 226829 - The breakpoint in the editor is not disabled
Summary: The breakpoint in the editor is not disabled
Status: RESOLVED DUPLICATE of bug 224649
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-28 11:08 UTC by satellite13
Modified: 2013-03-08 07:45 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (134.36 KB, text/plain)
2013-02-28 11:09 UTC, satellite13
Details

Note You need to log in before you can comment on or make changes to this bug.
Description satellite13 2013-02-28 11:08:56 UTC
If you put a breakpoint in the editor, then re-click the breakpoint icon does not remove breakpoints

Product Version = NetBeans IDE 7.3 (Build 201302132200)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_13
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.7-b01
Comment 1 satellite13 2013-02-28 11:09:03 UTC
Created attachment 132005 [details]
IDE log
Comment 2 Vladimir Riha 2013-02-28 11:40:29 UTC
Could you give more details? I know it could happen if page is running in embedded browser and if it such a case, I think it is duplicate of 224649
Comment 3 Vladimir Riha 2013-02-28 11:43:44 UTC
Btw the breakpoint can be removed from window "Breakpoints" (Window->Debugging->Breakpoints). But as described in issue 224649, the red line in editor will remain but code execution won't stop there.
Comment 4 satellite13 2013-02-28 11:49:52 UTC
Yes, this bug is a duplicate issue 224649
Comment 5 Vladimir Riha 2013-02-28 12:01:10 UTC
Thanks a lot for confirmation, so marking as a duplicate

*** This bug has been marked as a duplicate of bug 224649 ***
Comment 6 Vladimir Riha 2013-03-08 07:45:01 UTC
*** Bug 227125 has been marked as a duplicate of this bug. ***