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 72409 - Breakpoints gone fishing
Summary: Breakpoints gone fishing
Status: VERIFIED DUPLICATE of bug 52180
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-08 14:19 UTC by smil
Modified: 2006-10-23 16:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description smil 2006-02-08 14:19:45 UTC
during my work, I'm attaching and detaching the debugger from a server many times. 
After some detach-attach cycles the breakpoints in the editor gone hidden. They
are still there in the Breakpoints window. In this case I cannot disable them
clicking the line number. Clicking on it creates a new breakpoint. Disableing
that deletes only the new one.

I cannot tell the real reason yet. It can be in connection with
apply-code-changes function. I'm using that occaionally. 

This issue exists in 4.1 as well.
Comment 1 smil 2006-02-15 15:31:42 UTC
I think I found it. User error. It seems, that one class file has more than one
Java file attached.

For a odd reason, some of my classes are visible from more than one location.
The disappearing breakpoints seems to happen with these files. 

Anyhow, I can set a breakpoint in any of the files, but the breakpoint only
visible in the original place.

3 resolution possible:
- Use the package + classname for display as well like effective breakpoints
- Use file position always, like showing the breakpoints.
(- do nothing)

The display should be in sync with the state, even in soch cases.


Comment 2 Martin Entlicher 2006-06-28 16:09:33 UTC
You're right that this should be synced up. IMHO this is a dupl. of issue
#52180. When you have another project with the same class, the debugger will not
stop there if all breakpoints are in the other class.

*** This issue has been marked as a duplicate of 52180 ***
Comment 3 Jiri Kovalsky 2006-06-28 19:26:43 UTC
Verified as duplicate issue.