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

Breakpoint being hit, but not breakpoint set #14947

Closed
sethladd opened this issue Nov 8, 2013 · 18 comments
Closed

Breakpoint being hit, but not breakpoint set #14947

sethladd opened this issue Nov 8, 2013 · 18 comments
Assignees
Labels
closed-cannot-reproduce Closed as we were unable to reproduce the reported issue
Milestone

Comments

@sethladd
Copy link
Contributor

sethladd commented Nov 8, 2013

Please see attached screenshot. There is no breakpoint in the gutter but a breakpoint is hit.


Attachment:
[Screen Shot 2013-11-07 at 7.28.21 PM.png](https://storage.googleapis.com/google-code-attachments/dart/issue-14947/comment-0/Screen Shot 2013-11-07 at 7.28.21 PM.png) (35.59 KB)

@sethladd
Copy link
Contributor Author

sethladd commented Nov 8, 2013

Also, no breakpoints in the breakpoints view


Attachment:
[Screen Shot 2013-11-07 at 7.29.19 PM.png](https://storage.googleapis.com/google-code-attachments/dart/issue-14947/comment-1/Screen Shot 2013-11-07 at 7.29.19 PM.png) (12.56 KB)

@sethladd
Copy link
Contributor Author

sethladd commented Nov 8, 2013

For the record, I had a breakpoint there, but I double clicked to remove it. It looks removed to me.

@clayberg
Copy link

clayberg commented Nov 8, 2013

cc @keertip.
Set owner to @devoncarew.
Added this to the M9 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium label.

@clayberg
Copy link

Removed this from the M9 milestone.
Added this to the 1.1 milestone.

@clayberg
Copy link

Removed this from the 1.1 milestone.
Added this to the 1.2 milestone.

@clayberg
Copy link

Removed this from the 1.2 milestone.
Added this to the 1.3 milestone.

@clayberg
Copy link

clayberg commented Apr 9, 2014

Removed this from the 1.3 milestone.
Added this to the 1.4 milestone.
Removed Priority-Medium label.
Added Priority-High label.

@kasperl
Copy link

kasperl commented May 8, 2014

Removed this from the 1.4 milestone.
Added this to the 1.5 milestone.

@devoncarew
Copy link
Member

I think this is an issue with the breakpoints in dartium getting out of sync with those in the editor. I'll move this out of 1.5 and see if I can repo it.

@devoncarew
Copy link
Member

Removed this from the 1.5 milestone.
Added this to the 1.6 milestone.
Removed Priority-High label.
Added Priority-Medium label.

@DartBot
Copy link

DartBot commented Jun 5, 2014

This comment was originally written by @zoechi


I had this mostly when Dartium does its 'Aw Snap' when hitting a breakpoint
which was rather often at some times.
The main problem is that sometimes I wasn't able to get rid of these breakpoints, not even restarting Dartium and DartEditor solved it.
The only way to work around this was to move the code so that the breakpoint is on an empty line. (Not funny if you use Git or other VCS)

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-1.6 label.

@sethladd
Copy link
Contributor Author

Will return to repro.


Added Editor-Debugging label.

@DartBot
Copy link

DartBot commented Aug 22, 2014

This comment was originally written by @zoechi


I have this problem less often and recently 'delete all breakpoints' in the breakpoints window solved this. The breakpoint synchronization (DartEditor Dartium) seems to be under heave development. It changed very often in the bleeding edge versions the past weeks. It seems to become better and better with some relapse in between.

@clayberg
Copy link

cc @scheglov.

@scheglov
Copy link
Contributor

cc @devoncarew.
Set owner to @scheglov.
Added CannotReproduce label.

@clayberg
Copy link

Added this to the 1.7 milestone.

@sethladd sethladd added Type-Defect closed-cannot-reproduce Closed as we were unable to reproduce the reported issue labels Sep 27, 2014
@sethladd sethladd added this to the 1.7 milestone Sep 27, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-cannot-reproduce Closed as we were unable to reproduce the reported issue
Projects
None yet
Development

No branches or pull requests

6 participants