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 202806 - [71cat] breakpoint moves
Summary: [71cat] breakpoint moves
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Martin Entlicher
Depends on:
Reported: 2011-09-29 08:29 UTC by muellermi
Modified: 2012-06-13 08:55 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 muellermi 2011-09-29 08:29:48 UTC
Product Version = NetBeans IDE Dev (Build 201109260601)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0
Runtime = Java HotSpot(TM) Client VM 21.0-b17

sometimes, and I haven't figured out how to reproduce, if you edit (add/remove lines), set a breakpoint (without storing at this time) and start the app, the breakpoint moves up or down some lines. Often this leads to a non-applicable breakpoint.
Comment 1 Milutin Kristofic 2011-10-04 09:20:37 UTC
Changing a category to debugger -> Martin, do you have any more concrete issue similar to this one?
Comment 2 muellermi 2011-10-06 07:48:20 UTC
Today, I could reproduce this problem:

I have a very samll class for testing purrpose:

public class ParamManager {

    private FacesContext _context;

    private void init() {
        _context = FacesContext.getCurrentInstance();  //#### breakpoint here####

    public String getParam(String param) {
        return _context.getExternalContext().getInitParameter("upload.root");//#### breakpoint here####

start debugging - everything is ok
next add @Named Annotation. This annotation requires an additional import.
start debugging, at least one breakpoint moves

delete or add some lines _before_ the class: same problem

comclusion: breakpoint move happens when the linecount before the class is changed
Comment 3 Martin Entlicher 2011-10-06 17:13:52 UTC
Thanks for the description.
Comment 4 Martin Entlicher 2012-06-13 08:55:52 UTC
It looks like this was fixed by
It behaves fine for me in recent dev builds.