-
Notifications
You must be signed in to change notification settings - Fork 218
Support debugging in IntelliJ #459
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
Comments
/cc @stevemessick |
IntelliJ IDEA supports debugging in Firefox. I never tried and didn't look in the related code, but I suppose the answer is 'yes' for Firefox. Safari and IE - No. |
I haven't been able to get debugging to work in Firefox. Tried dozens of times and so have several coworkers. Debugging in Dartium works about a tenth of the time. |
@alexander-doroshko I've added a task for finding the remote debugger URL for Firefox. @vpigrad I expect the IntelliJ team would be very interested in hearing your bug reports, but I don't think this is the place. Alexander, where can they follow up to send y'all more information? |
@vpigrad Debugging Dart in Firefox has never been tested, not sure it ever worked. Debugging should work in Chromium-based browsers. Issue tracker link: https://youtrack.jetbrains.com/issues/Web, subsytem: Dart. @nex3 Firefox-related part is low priority. |
@devoncarew who has been working on some of the debugger source in IJ |
That's not a good way to debug VM tests. Debugging should only be done through the explicit interface provided by the test runner. At some point, I'm going to reimplement |
That's exactly what dart-lang/pub#1204 is about. As soon as dart-lang/pub#1204 is done users will be able to debug any app started via
Of course I'm also happy with debugging using explicit interface provided by the test runner, and this approach has certain advantages. |
This is not officially supported either; you should only ever invoke pub by running the wrapper script. In fact, I'd say that invoking the snapshot is likely to break once dart-lang/sdk#24736 is fixed. |
Looking at that list above, I'm not sure Firefox is a priority; being able to debug VM tests would be higher on my list. I'd also de-prioritize Dartium, and add debugging of Flutter tests (which are also service-protocol based). Given that we have a full featured command-line debugger, the work to debug VM tests should be pretty tractable. Hereabouts: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/test/flutter_platform.dart#L170, flutter is able to run tests, open a service protocol port, and connect to it for the purposes of grabbing coverage data. We should be able to use a similar technique to connect, set breakpoints, and debug. |
@devoncarew I'm not worried about Firefox being difficult to support. I agree that VM debugging is important, but it's blocked; see #50. Flutter support isn't part of the core test package; they maintain a separate plugin. If their plugin emits an |
OK, |
Feel free to put something on my calendar, preferably in the afternoon. |
If I can chime in for a moment as a user (and proponent) of Dart and Thanks, On 9/28/16 1:21 PM, Devon Carew wrote:
|
Based on my conversation with @jwren, @devoncarew, and @kevmoo here are the components of debugging support we need:
IntelliJ folks: do you have the means to interact with with Firefox, Safari, or IE's remote debuggers? Right now we only have logic for extracting information from Chrome- and Dartium-alikes, but if it's possible to do so for other browsers and it would be useful, we can expand that.
The text was updated successfully, but these errors were encountered: