Breakpoints not working in Ubuntu Distro about eclipse3 HOT 6 OPEN

Comment by floitschG

Added Area-VM, Triaged labels.

from eclipse3.

Comment by iposva-google

It is not entirely clear to me from your description how your statement of "not triggering breakpoints" and the exception trace you posted are connected.

Would you mind posting exact steps to reproduce your problem? In the meantime I will assign this to the Dart analyzer team from where this stack trace originates.

cc @danrubel.
Removed Area-VM label.
Added Area-Analyzer, NeedsInfo labels.

from eclipse3.

Comment by bwilkerson

Fixed the exception from the stack trace in https://codereview.chromium.org/1113063007/ (bleeding edge revision 45493). Someone needs to investigate the debugging issue.

Removed Area-Analyzer label.
Added Area-Editor, Triaged labels.

from eclipse3.

Comment by clayberg

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

from eclipse3.

This comment was originally written by [email protected]

I meant that the breakpoints are not working at all. No matter where you place the breakpoint the breakpoints, they do not get triggered.

The steps I was able to create the issue is.

1)Place a breakpoint on a method that you are sure the breakpoint will be triggered when the app runs.

2. Run the app

3. The app will continue to work but the breakpoints will not be triggered eventhough they are placed.

While investigating the issue, I went to the dart folder and ran the dartEditor from the command line. The stack trace was displayed on the command line after the I ran the application.

from eclipse3.

Comment by jeffascentis

Confirmed still broken in 1.10.1.

from eclipse3.