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

debugger: allow the user to debug an app served from their own server #3748

Closed
devoncarew opened this issue Jun 19, 2012 · 19 comments
Closed
Assignees
Milestone

Comments

@devoncarew
Copy link
Member

Right now we serve apps from an embedded server in the editor, and - because of our reliance on these specific urls - can only debug apps served from our server. A common use case is to run your own server and serve your web app files from that. There's no technical reason why the editor should not be able to debug these apps as well.

@danrubel
Copy link

Set owner to @devoncarew.
Removed Type-Defect label.
Added Type-Enhancement label.

@keertip
Copy link
Contributor

keertip commented Jun 19, 2012

Set owner to @keertip.

@keertip
Copy link
Contributor

keertip commented Jul 11, 2012

The editor now has the ability to set breakpoints and resolve and display source while debugging from url launches.


Added Fixed label.

@DartBot
Copy link

DartBot commented Oct 26, 2012

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


Has this issue been fixed? It still appears to be broken in Dart Editor 13841.

@keertip
Copy link
Contributor

keertip commented Oct 26, 2012

@tstief,

Yes, this has been fixed. You can specify a url in the launch configuration and should be able to debug the application.

What is the issue you are seeing?


Removed this from the M1 milestone.
Added this to the M2 milestone.
Added Triaged label.

@keertip
Copy link
Contributor

keertip commented Nov 7, 2012

Reopen as neccessary


Added Fixed label.

@DartBot
Copy link

DartBot commented Dec 26, 2012

This comment was originally written by nistvan.8...@gmail.com


Could you please give us some details how Chromium registers breakpoints coming from the Dart Editor? For me it seems that if i use an external HTTP server to provide the HTML page - which's Dart code has breakpoints - it can't be anywhere on the server. From my experiments it has to be exactly in the same directory layout (under the server's root?) as it is in the Dart project folder. Eg. if i have a HTML file in my project called 'dart_project' as dart_project/web/index.html i have to serve it up as http://localhost/dart_project/web/index.html else breakpoints will not going to work because i guess something doesn't match up with the breakpoint registrations.

What if i would like to server my index.html page right in the server's root? Currently i can't debug the application like that. I think we need more options to customize this debugging method.

@DartBot
Copy link

DartBot commented Feb 4, 2013

@DartBot
Copy link

DartBot commented Mar 24, 2013

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


Dart Editor version 0.4.2_r20259
Dart SDK version 0.4.2.8_r20259
Dartium Version 27.0.1430.0 (186115)

I am having trouble with this too. I have a dart server running http://127.0.0.1:1337 and a launch configuration with http://127.0.0.1:1337/board.html. The dart server is doing the static file serving so that I don't run into cross origin restrictions when . The break points are never hit.

I plan on trying the tip in comment #­8, but is what I've setup supposed to work?

@DartBot
Copy link

DartBot commented Mar 27, 2013

This comment was originally written by olivier.nouguie...@gmail.com


IMHO in In M3 the bug should be reopened.
Or the #­7 limitation is still true :(
(I have disable the chromium security)

@DartBot
Copy link

DartBot commented May 3, 2013

This comment was originally written by off...@mikemitterer.at


I had the same problem with M4. #­7 is a workaround but no solution. Bug should be reopened.
My problem here on Stackoverflow: http://stackoverflow.com/questions/16358773/debugging-a-dart-webapp-with-launch-target-url-fails

Priority should go to High. Workaround is nice but useless for real world WebApps.

@madsager
Copy link
Contributor

madsager commented May 6, 2013

Reopening for triage.


Added Triaged label.

@madsager
Copy link
Contributor

madsager commented May 6, 2013

Issue #10427 has been merged into this issue.

@devoncarew
Copy link
Member Author

Set owner to @devoncarew.
Added Started label.

@devoncarew
Copy link
Member Author

Removed this from the M2 milestone.
Added this to the M5 milestone.

@devoncarew
Copy link
Member Author

This is fixed in continuous, and will be in the next weekly release.

We've added a source directory parameter in the launch configuration dialog. When you specify a url launch, you'll also need to include the source directory to resolve the sources from. This will generally be the <project-name>/web directory. So if your url is http://localhost:1234/index.html and you specified <project-name>/web as the source directory, we'll look for http://localhost:1234/foo/bar.dart in <project-name>/web/foo/bar.dart.


Added Fixed label.

@DartBot
Copy link

DartBot commented Jun 10, 2013

This comment was originally written by off...@mikemitterer.at


Still does not work.

Dart Editor version 0.5.13_r23552
Dart SDK version 0.5.13.1_r23552

My structure is:


packages
test
lib/src/presenter.dart
WebContent/crud.html
WebContent/assets/dart/client.rest.dart
...

It' possible to debug client.rest.dart but not presenter.dart.

My settings are:
URL: http://localhost:8080/crud.html

Source location:
/WebApp.Base/WebContent

@devoncarew
Copy link
Member Author

Removed this from the M5 milestone.
Added this to the M6 milestone.
Removed Type-Enhancement label.
Added Type-Defect, Triaged labels.

@devoncarew
Copy link
Member Author

Removed this from the M6 milestone.
Added this to the M7 milestone.

@devoncarew devoncarew self-assigned this Aug 15, 2013
@devoncarew devoncarew added this to the 1.1 milestone Aug 15, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants