Eclipse Debug Configuration should allow host as well as port

AlexRee / chromedevtools

Automatically exported from code.google.com/p/chromedevtools

BSD 3-Clause "New" or "Revised" License

0 stars 0 forks source link

Eclipse Debug Configuration should allow host as well as port #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Google Chrome version: dev channel
SDK + Eclipse Debugger version(s): 3.5 golden
OS + version: Mac OSX 10.5

What steps will reproduce the problem?
1. From the Eclipse debug tool icon drop down, select "Debug 
Configurations..." 
2. Select "Chromium JavaScript", and select context menu item "New"

What is the expected result? In addition to Port: I expected to see Host: to 
allow me to remote debug.

What happens instead? No Host: entry field.

Please provide any additional information below. If possible, attach a
(reduced) test-case.

Original issue reported on code.google.com by pmue...@gmail.com on 5 Aug 2009 at 2:13

GoogleCodeExporter commented 9 years ago

Currently, due to the security concerns, connections are allowed only from the 
localhost. There are plans (no definite timeline) to enable remote connections, 
too.

Original comment by apav...@chromium.org on 13 Aug 2009 at 8:50

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

apavlov just asked me on IRC what my urgency on this was.  None.  Just seemed 
like an 
obvious thing to do, eventually.

Original comment by pmue...@gmail.com on 16 Feb 2010 at 6:34

GoogleCodeExporter commented 9 years ago

Easy workaround is to use transparent proxy such as tcpproxy.js, 
see end of this page:

http://wiki.github.com/ry/node/using-eclipse-as-node-applications-debugger

This technique can be used both for browser and server side V8 scripts.

Original comment by ztomi...@gmail.com on 26 Feb 2010 at 1:14

GoogleCodeExporter commented 9 years ago

Issue 29 has been merged into this issue.

Original comment by apav...@chromium.org on 12 Apr 2010 at 2:53

GoogleCodeExporter commented 9 years ago

This is actually a major issue when it comes to NodeJS and embedded V8 
developers out there. I would very much like to see this one implemented, would 
make life 10x easier.

Original comment by MRares on 10 Nov 2010 at 8:15

GoogleCodeExporter commented 9 years ago

A good point! Narrowing it down to "Standalone V8" case makes it easier to 
handle. No need to deal with Chromium security story.

Original comment by peter.ry...@gmail.com on 10 Nov 2010 at 8:26

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Should be fixed in HEAD.

Original comment by peter.ry...@gmail.com on 28 Jan 2011 at 6:04

GoogleCodeExporter commented 9 years ago

Fixed in 0.2.2

Original comment by peter.ry...@gmail.com on 18 Feb 2011 at 8:44

Changed state: Fixed