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 155238 - Do not show breakpoint if it was not set
Summary: Do not show breakpoint if it was not set
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Martin Entlicher
Keywords: UI
Depends on:
Reported: 2008-12-11 14:50 UTC by Ivan Sidorkin
Modified: 2012-10-10 12:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Sidorkin 2008-12-11 14:50:10 UTC
Product Version: NetBeans IDE Dev (Build 200812040201)
Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

- create Mobile application
- in HelloMIDlet switch to source view
- add breakpoint to line 16 ( private boolean midletPaused = false; )
- create Mobile application
- in HelloMIDlet switch to source view

breakpint set to line 16
Comment 1 Petr Suchomel 2009-02-26 09:37:33 UTC
Ivan, could you explain this report? I am not sure I do understand.
Comment 2 Ivan Sidorkin 2009-02-26 10:54:58 UTC
you have 2 projects (ME projects) each of them has file with same name (
both files opened in source view

add breakpoint to one file.
it added, you can see icon in gutter 
switch to second file, you can see breakpoint icon at the same line, but it shouldn't be there
Comment 3 Denis Anisimov 2009-03-23 11:20:37 UTC
All debugger UI belongs to Java debugger because files has mime-type "text/x-java" .
Setting breakpoint actions and annotations are handled by JPDA debugger.

It seems org.netbeans.modules.debugger.jpda.projects.BreakpointAnnotationProvider
somehow incorrectly set debugger annotations.
So this is not J2ME issue.
Comment 4 Martin Entlicher 2009-03-23 12:13:19 UTC
This is a field breakpoint, right? Currently we do not distinguish the URL of the source file, field breakpoint is just
set on the class and field name. Wherever the source is.
Thus we'd need to associate the field (and method, class, exception, etc.) breakpoints with the project.
Comment 5 Martin Entlicher 2012-05-22 12:01:27 UTC
IMHO the priority is lower than P3. Usually this does not cause any harm.
To solve this, we'd have to add some field for project URL to the field/method/class/exception breakpoint customizer. It would activate the breakpoint in the debugger session only if the given project, or it's "parent" project, is being debugged.