Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dart editor ignores all breakpoints under Windows #23032

Closed
DartBot opened this issue Mar 30, 2015 · 11 comments
Closed

Dart editor ignores all breakpoints under Windows #23032

DartBot opened this issue Mar 30, 2015 · 11 comments
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures
Milestone

Comments

@DartBot
Copy link

DartBot commented Mar 30, 2015

This issue was originally filed by Med...@gmail.com


What steps will reproduce the problem?
1.Set a breakpoint to any line of code

What is the expected output? What do you see instead?

  1. Program runs through the breakpoint without stop. I would expect it to stop.

What version of the product are you using?
Dart Editor 1.9.1

On what operating system?
Windows 7, 64 Bit

What browser (if applicable)?
Dartium opened by Dart Editor

Please provide any additional information below.

I can see debug info in Dart Editor, and a runtime error does stop at the code it says, but breakpoints I set is just being ignored!
I tried to remove .dartium & DartEditor folder under C:\Users[USER].
I tried to open Developer Tool in Dartium and close it to force it <debugger connection resumed>.
I tried re-download Dart Editor again, but got no luck at all.
I did installed some Chrome Extensions before this issues occurs, but I disabled all newly installed Chrome Extensions, and still no luck then.

@lrhn
Copy link
Member

lrhn commented Mar 30, 2015

Added Area-Editor, Triaged labels.

@clayberg
Copy link

cc @keertip.
Set owner to @devoncarew.
Removed Priority-Unassigned label.
Added Priority-Medium label.

@clayberg
Copy link

cc @devoncarew.
Set owner to @keertip.

@DartBot
Copy link
Author

DartBot commented Mar 31, 2015

This comment was originally written by MediaKid...@gmail.com


More Info:

I roll-backed to version 1.8.5, then breakpoints stop as expected.
I tried to exit 1.8.5 and run with 1.9.1, breakpoints are ignored again.

@danrubel
Copy link

Added this to the 1.10 milestone.
Removed Priority-Medium label.
Added Priority-High label.

@DartBot
Copy link
Author

DartBot commented Mar 31, 2015

This comment was originally written by di...@yahoo.com_


In case it's relevant, I've also been seeing this problem on Win 7 64-bit (I have no other platform to try it on).

@DartBot
Copy link
Author

DartBot commented Mar 31, 2015

This comment was originally written by Media...@gmail.com


More Info:

It's me again,I tried Dart Editor 1.9.1 on my Mac OSX 10.10.2. I got the same problem!

@keertip
Copy link
Contributor

keertip commented Mar 31, 2015

@Mediakid,

Can you reproduce the issue using the pop pop win sample?

@clayberg
Copy link

Changed the title to: "Dart editor ignores all breakpoints under Windows".

@DartBot
Copy link
Author

DartBot commented Mar 31, 2015

This comment was originally written by di...@yahoo.com_


@keertip - I can reproduce the problem with the pop pop win sample. I tried placing breakpoints at the startGame() call in game_web.dart and in the constructor for PlatformWeb in platform_web.dart. The game runs fine, but the breakpoints never trigger. (I also first encountered this problem directly after updating to 1.9.1 release. I had been using 1.8.5 release before that as well as earlier dev builds of 1.9 which I believe did not have the problem.).

@keertip
Copy link
Contributor

keertip commented Mar 31, 2015

@DartBot DartBot added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures labels Mar 31, 2015
@DartBot DartBot added this to the 1.10 milestone Mar 31, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

5 participants