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 149364 - Debugger runs to cursor after pressing Continue
Summary: Debugger runs to cursor after pressing Continue
Status: RESOLVED WONTFIX
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: _ deva
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-07 13:35 UTC by Roman Mostyka
Modified: 2012-09-03 08:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2008-10-07 13:35:04 UTC 
1. Create web application with JSF framework.
2. Add JavaScript file.
3. Set several breakpoints for this file.
4. Debug it and do the action, which suspends debugger. Debugger is suspended on the first breakpoint.
5. Set cursor somewhere after all breakpoints and press F4 (run to cursor).
6. Debugger doesn't run to cursor, it suspends on the next breakpoint.
7. Pressing F5 for all next breakpoints.

Result: Debugger suspends on the line, which were selected during run to cursor action, but after F5 (Continue) were
pressed.
Comment 1 _ krystyna 2008-10-07 13:47:18 UTC 
HI Roman, can you mark your bugs with the specific browser you used? Thanks.
Comment 2 Roman Mostyka 2008-10-07 14:19:14 UTC 
Hi Krys! In the beginning I was thinking are you ever sleeping. :) But then I've remembered that you in Prague now. :)
I used Internet Explorer with Windows XP. I don't know can it help, since I think the problem is in the code, not in plugin.
Comment 3 _ deva 2008-10-07 16:19:01 UTC 
I think it is the expected behavior to stop at a breakpoint. Have you tested this with Java debugging?
Comment 4 Quy Nguyen 2008-10-07 17:05:38 UTC 
Firefox debugging works the other way - all breakpoints are ignored until the cursor is hit or the current JavaScript
execution is completed.
Comment 5 Roman Mostyka 2008-10-07 17:12:48 UTC 
No, I didn't. But after your comment I've tried and I see the same behavior. But I'm still not sure that this behavior
is good. If user wants to run to cursor I guess it is expected that user is aware about all breakpoints, but don't want
to stop on them.
And FireBug plugin for FireFox works different.
Comment 6 _ deva 2008-10-07 17:21:58 UTC 
The behavior of IE is consistent with what happens when you step out. It does stop at the breakpoints even when the user
intends to move into the calling method. I will experiment with other debuggers to see the behavior.
Comment 7 Quy Nguyen 2008-10-07 17:34:36 UTC 
It makes sense for Java debugging to hit all other breakpoints - otherwise, if for some reason the line is never
reached, the Java debugger would never hit any breakpoints for the remainder of the debugging session.
Comment 8 Martin Entlicher 2012-09-03 08:31:56 UTC 
A new implementation of JavaScript debugger is in trunk. Closing old issues.