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.
Step to reproduce: 1. Create JSP file and compile it. 2. Add a breakpoint to JSP. 3. Switch to servlet view and remove servlet breakpoint by clicking on the left pane of editor. 4. Switch to JSP view and place cursor below a breakpoint. 5. Press F4 button to start debug ("run to cursor"). Expected result: Debugger starts and stop on breakpoint, above a cursor. Actual result: Debugger do not stops on breakpoint and stops only in current line. Well reproduced on W2K & RH Linux 7.2 with FFJ 4.0 rc4 P.S. The same situation if I start debug by pressing F4 button on generated servlet.
as designed - the JSP breakpoint represents the real breakpoint - every compilation generats the servlet breakpoint, which represents the jsp breakpoint in the generated servlet, because the generated servlet is every compilation new so if you delete the servlet breakpoint and do not recompile the jsp, debugger will not stop this is usefull, when you play with some page and just before next compilation you want to do not use some breakpoints temporally
Hi Damian, I mean that such type of breakpoints may confuse user. User want to debug JSP file and place cursor under breakpoint. Debugger do not stops on this breakpoint. So, when I delete breakpoint inside generated servlet, corresponding breakpoint should be deleted inside JSP. Should I submit new bug for it?
reop
This bug was fixed. Debugger stops on nearest line of code. Cannot reproduce with current Netbeans dev build (200302191342).
Verified with current Netbeans dev build (200302191342).
Resolved for 3.4.x or earlier, no new info since then -> closing.