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.
It emerged after fixing issue #45360. If you stop on breakpoint inside tag, following debugging is not working properly. To reproduce: Create custom tag and put it to JSP with some context (like in issue #45360). Put breakpoint inside tag. Put second breakpoint to the end of JSP. Start debugger. Debugger will stop on first breakpoint inside tag. If you now press F7 or F8 second breakpoint will be always reached and all jsp code before second breakpoint will be skipped. If you put second tag after first one and press F7 after reaching breakpoint inside first tag, second tag will be "somehow" debugged.
I must be missing something. I tried it on JDK1.4.2_05 and JDK1.5beta2 and it works fine for me.
Works fine on linux + JDK1.5, too. I realize you tested on Windows, so I'm gonna try on windows.
This happens only on combination of JDK 1.5 (I used the latest RC build) and Windows, no matter if socket or shared memory is used. Other systems or other JDKs work fine. To me it seems this can be partially connected to 46682? Reassigning to dbgjpda for deeper evaluation - tell me if you need some more info. I'll attach the web project for easy reproduction: Just open the web project. Add breakpoints to index.jsp at lines 4 and 9 and Choose debug main project. When stopped on breakpoint, press F8. Expected is step to next line, what happens seems like a resume and debugger stops at next breakpoint.
Created attachment 17429 [details] Web Application Project
Reproducible on JDK1.5.0 FCS. Probably the same problem as in 49576.
*** This issue has been marked as a duplicate of 50315 ***
Adding same comment as to issue #46682: The bug which this bug is duplicate of is RESOLVED-WONTFIX, but I can't agree with this solution. As user I don't care whether the bug is in the IDE or JDK. And the JDK bug will not be likely fixed in JDK1.5.0_01. Is there any possibility to implement some workaround?
No known workarround on JDK1.5.0. You can use JDK1.4.x. *** This issue has been marked as a duplicate of 50315 ***
Sorry, I forgot to change component. I meant workaround in webapps code.
No known workaround for this one. I added RELNOTE keyword and it's the only thing we can do with it (besides pushing JDK team to fix it).
I have probably found some workarround, which is not so painful. The bug occurres during evaluation of expression loading a new instances of classes. Checking in src/org/netbeans/modules/debugger/jpda/expr/Evaluator.java; /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/expr/Evaluator.java,v <-- Evaluator.java new revision: 1.13; previous revision: 1.12 done
Works fine here, too.
verified
verified in build 200410311900