vpupkin / chromedevtools Goto Github PK

Title says it all.  

Would also be interested in any work-arounds as the remote debug appears to 
disable the native chrome dev tools.

Google Chrome version: 3.0.195.33
SDK + Eclipse Debugger version(s): Latest SVN
OS + version: Windows XP SP2

What steps will reproduce the problem?
1. Open browser on some page.
2. Start browser with debug port, open some other page.
3. Attach the debugger.
4. Close the page being debugged.

What is the expected result?
Debugger disconnects from the browser.

What happens instead?
Debugger continues to run as if nothing happened.

Please provide any additional information below. If possible, attach a
(reduced) test-case.
I provide a patch with desired behavior. I'm not a user of the debugger - we 
are trying to create 
our own debugger based on this code. Please introduce the closeTab protected 
method so we 
can override it if this behavior is as designed or the fix is not as simple as 
I thought.

Google Chrome version: 11.0.696.16
SDK + Eclipse Debugger version(s): 0.2.2
OS + version: Ubuntu 10.10

What steps will reproduce the problem?
1. Copy the attached files to some local folder.
2. Start Chrome and open index.html file in it.
3. Run 'Chromium JavaScript' debug configuration in Eclipse
4. Open node corresponding to the debug configuration in 'Project Explorer'

What is the expected result?
Both index.html and funs.js files should be shown in 'Project Explorer'

What happens instead?
Only funs.js is shown.
However if we put a breakpoint inside funs.js and refresh page in Chrome the 
debugger will stop on the breakpoint and both index.html and funs.js files will 
be shown in 'Project Explorer'.

It appears that DebugEventListener#scriptLoaded event is fired for scripts in 
*.js files but isn't fired for scripts in *.html files until debugger stops on 
a breakpoint.

Google Chrome version: 5.0.375.99
SDK + Eclipse Debugger version(s): 3.6/0.1.4.201001121950
OS + version: MacOSX Snow Leopard

What steps will reproduce the problem?
1. Connect the debugger to Chrome
2. Set some breakpoints in the scripts loaded into the New_configuration project
3. Disconnect (via Terminate or Disconnect)

What is the expected result?
The breakpoints remain set in the editor and in the Breakpoints view

What happens instead?
The breakpoints are gone, but oddly, the debugger in subsequent sessions stops 
on the corresponding lines

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

ChromiumLineBreakpoint currently hard-codes the debug model id to 
VProjectWorkspaceBridge.DEBUG_MODEL_ID. Since WorkspaceBridge 
implementations are able to supply their own model id, which is then used in 
other code, it'd be good to have ChromiumLineBreakpoint work in the same 
way.

Attached is a patch which implements that. Note that it does change 
ResourceManager to reference VProjectWorkspaceBridge.DEBUG_MODEL_ID. I 
didn't see a simple way for it to dynamically get the model ID, and in my 
WorkspaceBridge implementation I'm not using that class. It might be 
appropriate to consider both VProjectWorkspaceBridge and ResourceManager 
as part of a specific model implementation.

Currently the debugger can only connect to a browser running on localhost, as 
it's hard-coded in 
JavaScriptVmEmbedderFactory#connectToChromeDevTools(). Could this be modified 
to allow clients 
to pass the address?

We are developing IDE for Symbian WRT. Basically, we combine JSDT and 
ChromeDevTools and add 
our plumbing inbetween. So far it works really well. The code will be available 
under EPL and I think 
we will be able to discuss more at a later point.

Our goals is to reuse ChromeDevTools as much as possible. At this point we 
would like to make it 
possible the ChDT to use editors other then the one that is part of ChDT.

Patch modifies two classes:
LineBreakpointAdapter - changes getEditor accessibility from private to 
protected. This allows easy 
creation of the subclasses that work with other editors.
JsDebugModelPresentation - getEditorId now calls IDE.getEditorDescriptor to 
pick the editor for 
provided element. This will pick the Chrome editor for the files with ".chrome" 
extension, JSDT 
editor for JS file, HTML editor for HTML, etc. So far the testing did not show 
any problems.

Google Chrome version: Any
SDK full version: 0.1.0.200907072135
OS + version: Any

What steps will reproduce the problem?
1. Set a breakpoint in a script file
2. Reload the tab being debugged

What is the expected result?
The breakpoint is retained in the script file

What happens instead?
The breakpoint disappears and does not get hit during debugging.

Please provide additional information below. If possible, attach a
(reduced) test-case.
1) The breakpoints are set by script IDs rather than names (which is 
nevertheless useful for V8 duplicate scripts) and
2) They are associated with resources that get removed and re-added when 
the tab is reloaded

Google Chrome version: 11.0.696.50 beta
SDK + Eclipse Debugger version(s): 0.2.2
OS + version: Ubuntu 10.10

What steps will reproduce the problem?
1. Connect to Chrome instance using the API, set a breakpoint in some file.
2. When the breakpoint is reached, obtain value of some local variable 
from DebugContext using getCallFrames(), getVariablesScopes(), getVariables() 
methods.
3. Change value of the variable using 
CallFrame#getEvaluateContext().evaluateAsync("varName=newvalue",...) method 
call.
4. When value is changed try to obtain value of the variable from the 
DebugContext.

What is the expected result?

There should be a way to clear caches of DebugContext to fetch the new value.

What happens instead?

The cached old value is always returned.


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

It would be sufficient to add clearCaches() method to DebugContext class. 
However I think it would be better to automatically clear caches when methods 
like 'evaluateAsync' or JsVariable#setValue are called. I suppose there're not 
too much ways to change values when the debugger is suspended.

Google Chrome version: Chromium 5.0.375.99 (51029) Ubuntu 10.04

SDK + Eclipse Debugger version(s): Chromium JavaScript Remote Debugger Version: 
0.1.4.201001121950, Eclipse Version: 3.5.2 Build id: M20100211-1343

OS + version: Ubuntu Lucid

What steps will reproduce the problem?
1. Load a page through a localhost webserver in order to test behaviour
2. Step through and identify bugs
3. Try to edit, and discover there's no way to write your changes to the local 
files using the debugger view in Eclipse

What is the expected result?

The Eclipse Run Configuration should accept a manually provided mapping, e.g. 
between http://127.0.0.1:8000/ and file://var/www/html/ so that Eclipse can 
guess the local path of files loaded from the webserver. It could then view the 
local files, and allow edits to fix the bugs you find.

What happens instead?

I have to independently run another editor, manually navigate to the relevant 
file, and scroll through to find the same line in the local file then do the 
edit and reload. Nightmare.

Google Chrome version: 5.0.342.7 beta
SDK + Eclipse Debugger version(s): 3.5.2
OS + version: Mac OS X 10.5.x and 10.6.x

What steps will reproduce the problem?
1. Download latest Chrome Developer Tools from SVN
2. Establish debug session as outline on main project page

What is the expected result?
Prompt to select browser tab is shown.

What happens instead?
Connection takes forever and ends with "Timeout" exception from V8Helper.

The very same code works without any problems on Windows. The debugger was 
working before and it suddenly stopped 
working on all Mac machines.

There was a Chrome version update this week and it looks like it broke the 
debugger (we were testing debugger on 
Chrome all this time and it was working great). I tried to research the code 
and it looks like the connection is 
established, "version" request is sent but no response is ever received.

1. Install ZendStudio application ( http://www.zend.com/en/ ).
2. Install ChromeDevTools plug-in in Studio (which is essentially an Eclipse 
application).
3. Connect ChromeDevTools debugger to any stand-alone V8 application.
4. Open JavaScript file from a VirtualProject.
5. Try to set a breakpoint.

Expected:
Breakpoint is set and works.
Actual:
Nothing happens on mouse double-click or Ctrl+Shift+B. Corresponding items in 
menus are disabled.

Google Chrome version: n/a

SDK + Eclipse Debugger version(s): 0.1.3

OS + version: n/a

I believe there is buggy code in the JsonUtils.java

Go to:

http://code.google.com/p/chromedevtools/source/browse/trunk/plugins/org.chr
omium.sdk/src/org/chromium/sdk/internal/JsonUtil.java

Examine the function: getAsLong

The line:

 if (v instanceof Long || v == null) {

should be:

 if (v instanceof Long || v != null) {

There are more examples of this mistake in the file.

Google Chrome version: Chrome/14.0.814.0
SDK + Eclipse Debugger version(s):
Eclipse Modeling Tools
Build id: 20100218-1602
OS + version: XP SP3

What steps will reproduce the problem?
1. Install from ChromeDevTools Update Site - 
http://chromedevtools.googlecode.com/svn/update/dev/
2.
3.

What is the expected result?

Thought I should be able to install
Chromium JavaScript Debugger Bridge to JSDT 0.2.2.201102182139
as well, just like I was able to install the other three plugins:

    Chromium JavaScript Remote Debugger 0.2.2.201102182139
    ChromeDevTools Project Source Code  0.2.2.201102182139
    ChromeDevTools SDK  0.2.2.201102182139

What happens instead?

Cannot complete the install because one or more required items could not be 
found.
  Software being installed: Chromium JavaScript Debugger Bridge to JSDT 0.2.2.201102182139 (org.chromium.debug.jsdtbridge.feature.group 0.2.2.201102182139)
  Missing requirement: Chromium JavaScript Debugger Bridge to JSDT 0.2.2.201102182139 (org.chromium.debug.jsdtbridge 0.2.2.201102182139) requires 'bundle org.eclipse.wst.jsdt.core 1.1.0' but it could not be found
  Cannot satisfy dependency:
    From: Chromium JavaScript Debugger Bridge to JSDT 0.2.2.201102182139 (org.chromium.debug.jsdtbridge.feature.group 0.2.2.201102182139)
    To: org.chromium.debug.jsdtbridge [0.2.2.201102182139]
Please provide any additional information below. If possible, attach a
(reduced) test-case.

Google Chrome version:
SDK + Eclipse Debugger version(s): sdk 0.1.3 + eclipse n/a
OS + version: Windows XP and Windows 7

What steps will reproduce the problem?
1. Browser chromeBrowser = factory.create(addr, null);
2. tabFetcher = chromeBrowser.createTabFetcher();
3.

What is the expected result?
Should return a TabFetcher

What happens instead?
A NullPointerException is thrown

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

This method from the SocketConnectionFactory doesn't handle when the 
connectionLoggerFactory is null although the comments in the BrowserFactory 
create methods say that it may be null.

public SocketConnection newOpenConnection(NetListener netListener) throws 
IOException {
    SocketConnection connection = new SocketConnection(endpoint, 
connectionTimeoutMs,
       -> connectionLoggerFactory.newConnectionLogger() <-, handshaker);
    connection.setNetListener(netListener);
    connection.start();
    return connection;
  }

JavaScript Development Environment is a set of JS tools from eclipse.org (it is 
currently a part of WTP).

I believe Chrome Dev Tools users would benefit from integrated experience when 
they 
could use rich editing capabilities of the JSDT together with ChDT JS debugger.

We implemented similar functionality in our IDE 
(http://developer.symbian.org/main/source/packages/package/index.php?pk=263) 
and the 
source code is available under EPL. We would be glad to cooperate with Chrome 
Developer Tools project.

What we have:
1. Launch configuration type - will run Chrome and set the debugging session 
(i.e. add 
the breakpoint)
2. ChDT will work with JSDT editors - i.e. breakpoints can be set in JSDT 
editor (and 
stored between user sessions), stepping through the code will happen in JSDT 
editor, 
etc, stack view shows workspace resource names (instead of URLs), etc.

What is not in our code:
Our code relies on our requirements - i.e. it will expect HTML page with 
specific name 
in the project, Chrome is ran with lowered security, etc.

I would like to suggest discussing the requirements for "generic" JSDT 
integration. We 
will be glad to provide our code and help adopting it to new requirements.

Google Chrome version:
SDK + Eclipse Debugger version(s): 0.2.2 on Eclipse 3.6
OS + version: Windows 7, 64-bit

What steps will reproduce the problem?
1. Create debug target for node.js with nclosure installed and 'required'
2. Start target

What is the expected result?
Debugger attaches to node.js process

What happens instead?

Caused by: org.eclipse.core.internal.resources.ResourceException: < is an 
invalid character in resource name '<eval #113>.chromium'.
    at org.eclipse.core.internal.resources.Resource.checkValidPath(Resource.java:432)
    at org.eclipse.core.internal.resources.File.create(File.java:116)
    at org.eclipse.core.internal.resources.File.create(File.java:196)
    at org.chromium.debug.core.util.ChromiumDebugPluginUtil$4.tryCreate(ChromiumDebugPluginUtil.java:245)
    ... 20 more

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

I've modified ChromiumDebugPluginUti.java to handle '<','>' in addition to '?' 
characters. Patch below:


Index: ChromiumDebugPluginUtil.java
===================================================================
--- ChromiumDebugPluginUtil.java    (revision 647)
+++ ChromiumDebugPluginUtil.java    (working copy)
@@ -231,7 +231,7 @@
    *         has failed
    */
   public static IFile createFile(final IProject project, String filename) {
-    String patchedName = new File(filename).getName().replace('?', '_'); // 
simple name
+    String patchedName = new File(filename).getName().replaceAll("\\?\\<\\>", 
"_"); // simple name

     UniqueKeyGenerator.Factory<IFile> factory =
         new UniqueKeyGenerator.Factory<IFile>() {

Google Chrome version: 4.0.201.1
SDK + Eclipse Debugger version(s): 0.1.0.200907271854
OS + version: Win XP SP3

What steps will reproduce the problem?
1. Install subclipse
2. Have open projects associated with subversion repositories
3. Enable Quick Diff, using "pristine svn copy" as reference.

What is the expected result?
Javascript debugging works as expected

What happens instead?
Double clicking on a Google Chrome javascript file results in an error.
Switching perspectives results in screen display corruption with panels not 
updating.


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

(Earlier uncaptured error message was full of subversion classes. I've 
since upgraded to latest version of subversion, and the symptoms remained, 
but the stack trace changed)

Problems occurred when invoking code from plug-in: "org.eclipse.jface".

java.lang.NullPointerException
    at 
org.eclipse.jface.text.source.LineNumberRulerColumn.getWidth(LineNumberRule
rColumn.java:477)
    at 
org.eclipse.jface.text.source.LineNumberChangeRulerColumn.getWidth(LineNumb
erChangeRulerColumn.java:295)
    at 
org.eclipse.ui.internal.texteditor.LineNumberColumn.getWidth(LineNumberColu
mn.java:140)
    at 
org.eclipse.jface.text.source.CompositeRuler.getWidth(CompositeRuler.java:7
10)
    at 
org.eclipse.jface.text.source.SourceViewer$RulerLayout.layout(SourceViewer.
java:131)
    at 
org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1145)
    at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1534)
    at org.eclipse.swt.widgets.Canvas.WM_SIZE(Canvas.java:455)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4019)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2404)
    at 
org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
    at 
org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:4751)
    at 
org.eclipse.swt.widgets.Canvas.WM_WINDOWPOSCHANGED(Canvas.java:461)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4029)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
    at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1316)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2781)
    at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:893)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2742)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2738)
    at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:201)
    at 
org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1145)
    at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1534)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4019)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2404)
    at 
org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
    at 
org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:4751)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4029)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
    at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1316)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2781)
    at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:893)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2742)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2738)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2805)
    at org.eclipse.swt.custom.StackLayout.layout(StackLayout.java:120)
    at 
org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1145)
    at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1534)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4019)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2404)
    at 
org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
    at 
org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:4751)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4029)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
    at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1316)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2781)
    at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:893)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2742)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2738)
    at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:201)
    at 
org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1145)
    at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1534)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4019)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2404)
    at 
org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
    at 
org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:4751)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4029)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
    at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1316)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2781)
    at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:893)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2742)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2738)
    at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:201)
    at 
org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1145)
    at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1534)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4019)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2404)
    at 
org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
    at 
org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:4751)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4029)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589)
    at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
    at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1316)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2781)
    at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:893)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2742)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2738)
    at org.eclipse.swt.widgets.Control.setBounds(Control.java:2805)
    at 
org.eclipse.ui.internal.LayoutPart.setBounds(LayoutPart.java:300)
    at 
org.eclipse.ui.internal.presentations.PresentablePart.setBounds(Presentable
Part.java:170)
    at 
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.layoutCont
ent(PresentablePartFolder.java:131)
    at 
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.layout(Pre
sentablePartFolder.java:412)
    at 
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(Pre
sentablePartFolder.java:292)
    at 
org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftT
oRightTabOrder.java:65)
    at 
org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPa
rt(TabbedStackPresentation.java:473)
    at 
org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.ja
va:1256)
    at 
org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
    at 
org.eclipse.ui.internal.WorkbenchPage.internalBringToTop(WorkbenchPage.java
:789)
    at 
org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:613)
    at 
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.j
ava:2869)
    at 
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:276
2)
    at 
org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754)
    at 
org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705)
    at 
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at 
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701)
    at 
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685)
    at 
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676)
    at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651)
    at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610)
    at 
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUti
lity.java:361)
    at 
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUti
lity.java:168)
    at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:229)
    at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:208)
    at 
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDis
patchAction.java:274)
    at 
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAct
ion.java:250)
    at 
org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:
49)
    at 
org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221)
    at 
org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManag
er.java:202)
    at 
org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLin
kWithEditorHelper.java:48)
    at 
org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:842)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.runtime.Platform.run(Platform.java:888)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at 
org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:8
40)
    at 
org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java
:1101)
    at 
org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:467)
    at 
org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.ja
va:1205)
    at 
org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264)
    at 
org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258)
    at 
org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at 
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
    at 
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
    at 
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
    at 
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332
)
    at 
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
    at 
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at 
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication
.java:113)
    at 
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java
:194)
    at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
(EclipseAppLauncher.java:110)
    at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseA
ppLauncher.java:79)
    at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368
)
    at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179
)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)


eclipse.buildId=I20090611-1540
java.version=1.6.0_15
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_NZ
Framework arguments:  -product org.eclipse.epp.package.jee.product -product 
org.eclipse.epp.package.jee.product -product 
org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product 
org.eclipse.epp.package.jee.product -product 
org.eclipse.epp.package.jee.product -data E:\Workspaces\jboss -product 
org.eclipse.epp.package.jee.product

Currently Chromium Developer Tools require Java6 to properly build and run. 
This has some unfortunate implications on Mac as Java6 is 64-bit only on 
Mac and thus the only SWT variant is Cocoa64 that is lacking in several 
departments - i.e. it does not support embedding Mozilla browser, has 
higher memory requirement, etc.

Attached is a patch that enables the plugins to build and run on Java5. We 
did some pleriminary changes and found no problems.

Changes in the patch are:
1. Manifests were updated to include Java5 as valid run-time environment.
2. ChromiumIOException was introduced as java.io.IOException does not 
support ctors with Exception. I opted for introducing a new subclass so 
there is little changes to application behavior.
3. Handshaker::runnableFeature type was changed to FutureTask from 
RunnableTask - it was always its actual type. RunnableTask is not available 
in Java5 and is not a superclass of the FutureTask.

SDK/Debugger version: 0.3.0

The Script objects in the SDK always download their script data. This can 
significantly impact startup time for the debugger. Large scripts (600k-900k in 
our case) take around 1 sec to download even between processes on the same 
machine.

    JavascriptVm.getScripts(ScriptsCallback) throws MethodIsBlockingException;

In order to reduce the startup time of the debugger, I'd like the Script 
contents to only be loaded on demand, or to have additional API methods added 
to that you can determine which scripts are loaded into the target VM w/o 
downloading the content. In a nutshell, we want to know the script names, we 
don't use the script contents, and we don't want to pay the download cost for 
those contents. Thanks much!

Google Chrome version: 9.0.597.102
SDK + Eclipse Debugger version(s): Helios Service Release 1 Build id: 
20100917-0705
OS + version: Mac OS X Snow Leopard
Version of sources: latest from subversion, rev. 537

What steps will reproduce the problem?
1. Launch Chrome
2. Launch debugger
3. See the exception window saying "Timed out waiting for version"

Stacktrace:


java.io.IOException: Timed out waiting for version
    at org.chromium.sdk.internal.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:77)
    at org.chromium.sdk.internal.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:126)
    at org.chromium.sdk.internal.StandaloneVmImpl.attach(StandaloneVmImpl.java:71)
    at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$2$1.attach(JavascriptVmEmbedderFactory.java:121)
    at org.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:97)
    at org.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:84)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:923)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Somewhere in our web application (I will provide more information when I 
have it) we have a syntax error. This causes uncaught JS exception 
("Uncaught SyntaxError: Unexpected token"). The debug context does not have 
any frames so Chromium Developer Tools fail with exception:
Mar 2, 2010 11:10:16 AM 
org.chromium.sdk.internal.tools.v8.V8CommandProcessor
processIncomingJson
SEVERE: Failed to dispatch response to callback
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:546)
    at java.util.ArrayList.get(ArrayList.java:321)
    at java.util.Collections$UnmodifiableList.get(Collections.java:1155)
    at
org.chromium.debug.core.model.DebugTargetImpl.logExceptionFromContext(Debug
TargetImpl.java:417)
    at
org.chromium.debug.core.model.DebugTargetImpl.access$6(DebugTargetImpl.java
:415)
    at
org.chromium.debug.core.model.DebugTargetImpl$DebugEventListenerImpl.suspen
ded(DebugTargetImpl.java:399)
    at
org.chromium.sdk.internal.tools.v8.processor.BacktraceProcessor$1.success(B
acktraceProcessor.java:63)
    at
org.chromium.sdk.internal.DebugSession$ScriptLoader.loadAllScripts(DebugSes
sion.java:191)
    at
org.chromium.sdk.internal.tools.v8.processor.BacktraceProcessor.messageRece
ived(BacktraceProcessor.java:67)
    at
org.chromium.sdk.internal.tools.v8.V8CommandProcessor$2.call(V8CommandProce
ssor.java:116)
    at
org.chromium.sdk.internal.tools.v8.V8CommandProcessor.callThemBack(V8Comman
dProcessor.java:157)
    at
org.chromium.sdk.internal.tools.v8.V8CommandProcessor.processIncomingJson(V
8CommandProcessor.java:120)
...

Attached is a patch that avoids the NPE.

Google Chrome version: 5.0.356.0 dev
SDK + Eclipse Debugger version(s): 3.5.2
OS + version: Windows 7

What steps will reproduce the problem?
1. Install chromedevtools on clean from update site
2. Try to open any .js file with JS Editor 
3. Try to open any other file

What is the expected result?
I need edit files :)

What happens instead?
I can't edit files

Current timeout is hard-coded to 2 minutes, which is not always acceptable.

Google Chrome version: 3.0.195.0 (20616)
SDK full version: 0.1.0
OS + version: Any

What steps will reproduce the problem?
1. Load a URL into a tab and attach the Eclipse debugger
2. Reload the tab or navigate it to a different URL

What is the expected result?
Only the new URL scripts are saved into the target project

What happens instead?
All scripts from the previously loaded URLs appear in the target project 
along with the scripts from the current URL

Please provide additional information below.
The "scripts" V8 debugger command returns previously loaded scripts rather 
than the current URL's only. Currently the Eclipse debugger does not drop 
scripts missing in the "scripts" response, so once this issue is fixed with 
the V8 debugger, we should fix our side.

Subj

New debug protocol should provide all necessary data.

Google Chrome version: 3.0.196.2
SDK + Eclipse Debugger version(s): 0.1.0.200907271854
OS + version: WinXP SP3

What steps will reproduce the problem?
1. Run a webapp localy with maven jetty:run
2. User chrome to view the localy hosted project 
(http://localhost:8080/projectname)

What is the expected result?
Have javascript debuging informations


What happens instead?
I only get the protocol messages at the console and after a while all files 
from the project get's deleted

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

Google Chrome version:
SDK + Eclipse Debugger version(s):
OS + version:

What steps will reproduce the problem?
1.
2.
3.

What is the expected result?


What happens instead?


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

When starting a debug session a window pops up in which the tab to debug must 
be chosen.

It is not always obvious from the URL/text which tab to choose. 

The highlighted tab (one-click) in the Eclipse pop up window should also be 
"highlighted" in Chrome (i.e., tab taken to front and possibly highlight the 
whole tab like when inspecting elements in the native Chrome Developer 
Tools). 

A further enhancement could be to do this on hover and not just highlighting.

Currently the evaluate_javascript command is supported internally but not 
exposed as API. Attached is a 
patch to add an evaluateJavaScript() method to the org.chromium.SDK.BrowserTab 
interface. 

I took this approach because it seemed that the standalone v8 vm might not 
support it, so it could not be in 
a command interface. The idea is that a client would do a runtime instanceof 
check on 
org.chromium.sdk.JavascriptVm to see if it implements BrowserTab, and then cast 
to BrowserTab to invoke 
evaluateJavaScript().

This would really be best posted as a question in a dev mailing list, but I 
don't think there is one for 
this project, is there?

In class JsVariableImpl, the field variableFqn appears to be intended as the 
fully qualified name. But 
in practice it's not set and calling getFullyQualifiedName() doesn't return the 
appropriate value.

It would be very useful if this returned an name that could be used in 
expressions to set the variable 
value. Was that the intent here and would you be likely to accept a patch that 
addressed this?

SDK should provide additional API for such actions as
opening new tab,
closing tab,
changing url of a tab,
evaluating commands in tab.

Google Chrome version: ???
SDK + Eclipse Debugger version(s): 0.1.6 + 3.6
OS + version: Mac OS X Snow Leopard

What steps will reproduce the problem?
1. Try to get 0.1.6 working against latest build of Chrome
2. Fail
3. Try to figure out why
4. The project page, download page and page on version compatibility are 
cryptic with regards to versions of Chrome supported

What is the expected result?
Clear answer

What happens instead?
Confusion :-)

My current assumption, as current release of Chrome responds with error code in 
the V8 protocol, is that 0.1.6 on MacOSX does not yet have a release of Chrome 
browser that would support the protocol version that 0.1.6 bundles (correct me, 
if I am wrong in that assumption!)

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

I would suggest updating the compatibility page 
http://code.google.com/p/chromedevtools/wiki/VersionCompatibility with every 
release of Chrome dev tools, and making the table a bit clearer.

Google Chrome version: Any
SDK full version: 0.1.0
OS + version: Any

What steps will reproduce the problem?
1. Attach to any tab with JS code inside several <script> tags in the HTML

What is the expected result?
The HTML page is shown entirely, with the <script> tags, in a single file.

What happens instead?
The <script> tag contents are mapped onto different files.

Please provide additional information below.
The tab resources are not exposed through the ChromeDevToolsProtocol. Only 
script contents are downloaded through the V8 debugger protocol.

The user should be able to save a reference to any value in Variables or 
Expressions window. The value may be made persistent as property of global 
object.

Google Chrome version: 3.0.195.32
SDK + Eclipse Debugger version(s): r270 (HEAD)
OS + version: Ubuntu karmic & WinXP

What steps will reproduce the problem?
http://wiki.webvm.net/wrtc/m5.2-test-steps/ (Test 4)
1. Example page: http://wiki.webvm.net/wrtc/m5.2/
2. Put a break after label 2
3. It breaks two lines after it should have

What is the expected result?

Break on the right line

What happens instead?

Breaks on the wrong line

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

http://wiki.webvm.net/wrtc/m5.2-test-steps/ (Test 4)

Chromium reports a byte count for Content-Length in all communication coming 
from the browser, but SocketConnection treats the count as a character count. 
This causes the ConnectionLogger.LoggableReader.read to read into the next 
header if there is any utf8 characters in the content. The result is invalid 
JSON for this message, and an invalid destination for the next message because 
the next header is incorrect.

To duplicate, put the following into your JavaScript, and then debug.
// “”

There are 5 characters in the string. Chromium will report that there are 9 (3 
for: "// " + six for: e2 80 9c e2 80 9d)

The read will then read 9 chacters, which causes the read to continue into the 
next message header.

This does not fail on Windows, because the content gets converted into the 
following:
// \u201\u201d

I have not researched where in the communication layer this happens on the 
Chromium side.

The fix is either to:
1. SocketConnection and clients need to read bytes and then convert to 
characters after all content is read. Knowing that this really isn't needed for 
the Windows version.
or
2. Chromium on Macintosh needs to escape the script content as is done on 
Windows.

Class org.chromium.debug.ui.JsDebugModelPresentation is useful for clients 
which define their own debug model ID. These clients need to implement the 
"org.eclipse.debug.ui.debugModelPresentations" extension point and 
reference JsDebugModelPresentation. 

Currently this doesn't work because plugin org.chromium.debug.ui does not 
export any packages. Attached is a patch to export it.

What steps will reproduce the problem?
1. Connect to Chrome as "V8 standalone" application or vice versa.

What is the expected result?
Error message about unsuccessful handshake appears.

What happens instead?
"Timed out waiting for version" message appears. This is misleading.

SDK/Debugger version: 0.2.2
Eclipse version: -
Google Chrome/V8 Embedder + version: Chrome 13.0.782.107
OS + version: Ubuntu 11.04

What steps will reproduce the problem?
1. Connect to Chrome page
2. Stop debugger on a breakpoint
3. Add watch expression "localStorage.setItem('test', 'info')"; must evaluate 
to 'undefined'.
4. Add watch expression 'localStorage' and expand its properties

What is the expected result?
localStorage has property 'test' with a string value 'info'

What happens instead?
localStorage has property 'test' with an 'undefined' value.


Please provide additional information below. If possible, attach a
(reduced) test-case.
The problem should be in V8 debugger support. WIP (WebKit protocol) returns 
property correctly.

Google Chrome version: 13.0.782.107
SDK + Eclipse Debugger version(s): 3.7.0
OS + version: Ubuntu 11.04

What steps will reproduce the problem?
1. prepare a project and enter the following code as script
1. localStorage.setItem("test", "info");
2. localStorage.getItem("test");

What is the expected result?
localStorage.getItem("test") == "info"

What happens instead?
localStorage.getItem("test") == undefined


Is it possible to use this HTML5 feature? The problem is, that I need to 
write/read the localStorage, but I always get "undefined".

Google Chrome version: 4.1.249.1045
SDK + Eclipse Debugger version(s): 3.2.1, DevTools from current SVN
OS + version:

What steps will reproduce the problem?
1. Run Chrome
2. Connect debugger
3. Press Ctrl+Shift+I

What is the expected result?
Nothing happens

What happens instead?
Web inspector window should appear

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

I understand this is deliberate and has its reason. But it would be much 
easier to understand if there was some pop-up message that explains that 
debugger should be disconnected.

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.

What steps will reproduce the problem?
1. Create a variable with value that has 1000+ characters.
2. Try to see it in debugger.
3. Variable is truncated

This seems to be a Chrome issue - the value in Web Inspector is truncated 
just the same. It looks like the Eclipse-based debugger has currently no way 
to see full value.

Google Chrome version:
SDK full version:
OS + version:

What steps will reproduce the problem?
1. Start Eclipse with chromedevtools plugins installed.
2. Create a project (e.g. Java project), fill with important content.
3. Create "Standalone V8" or "Chromium JavaScript" debug configuration with
the same name as your project.
4. Start your debug configuration.

What is the expected result?
Your important project stays untouched.

What happens instead?
Debug configuration creates temporary project of its own name and
overwrites your important project.

In v. 0.2.2 live editing is not highly usable. 2 issues slow down the work:

1. "Push" actions is not easily accessible. One has to open context menu, then 
a submenu and choose a menu element, which is quite slow. A shortcut or even 
auto-push (push simply on a file save, perhaps with confirmation box) would 
make the feature a way more convenient.

2. Files under a virtual project are all read-only by default. User has to 
explicitly drop this attribute again and again after each live edit push. It 
would be nice to spare him from this.

Chrome developer tools fetch JS from the browser. In the case of HTML files 
this results in separate "resource" for each JS fragment that has 0 origin 
(see http://code.google.com/p/chromedevtools/issues/detail?id=2)

In our project we keep all HTML and JS sources in the user workspace so we 
need to let the user trace through the whole HTML page. We need to translate 
line number from the JS fragment using the fragment starting line as an 
offset.

Enclosed patch provides add-on developers an API to customize the line 
translation.

Google Chrome version: 2.0.172.39
SDK + Eclipse Debugger version(s):Eclipse Java EE IDE for Web Developers. 
Build id: 20090621-0832
OS + version: Windows XP Pro

What steps will reproduce the problem?

1. Start Chrome using a .bat file:
cd C:\Documents and Settings\34854Do\Local Settings\Application 
Data\Google\Chrome\Application
call chrome.exe --remote-shell-port=9222

2.Start an Eclipse debug session

What is the expected result?

A debug session starts

What happens instead?

An error dialog appears. The log is this:

java.lang.NoSuchMethodError: java.io.IOException: method 
<init>(Ljava/lang/String;Ljava/lang/Throwable;)V not found
at org.chromium.sdk.internal.BrowserImpl.connect(BrowserImpl.java:183)
at org.chromium.debug.ui.launcher.LaunchType.launch(LaunchType.java:69)
at 
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurat
ion.java:853)
at 
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurat
ion.java:703)
at 
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.ja
va:866)
at 
org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

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

I'm using source build as of December 9th, 2009.

Debugger fails to show the variables when the breakpoint is hit. Relevant stack 
trace is:
Caused by: org.chromium.sdk.internal.protocolparser.JsonProtocolParseException: 
Failed to 
parse field name
    at 
org.chromium.sdk.internal.protocolparser.dynamicimpl.JsonProtocolParser$LazyPars
eFieldMetho
dHandler.parse(JsonProtocolParser.java:571)
    at 
org.chromium.sdk.internal.protocolparser.dynamicimpl.JsonProtocolParser$LazyPars
eFieldMetho
dHandler.parse(JsonProtocolParser.java:562)
    at 
org.chromium.sdk.internal.protocolparser.dynamicimpl.JsonProtocolParser$LazyPars
eFieldMetho
dHandler.handle(JsonProtocolParser.java:547)
    ... 22 more
Caused by: org.chromium.sdk.internal.protocolparser.JsonProtocolParseException: 
Field must 
have type java.lang.String
    at 
org.chromium.sdk.internal.protocolparser.dynamicimpl.JsonProtocolParser$SimpleCa
stParser.par
seValueQuick(JsonProtocolParser.java:629)
    at 
org.chromium.sdk.internal.protocolparser.dynamicimpl.JsonProtocolParser$LazyPars
eFieldMetho
dHandler.parse(JsonProtocolParser.java:569)
    ... 24 more
Caused by: java.lang.ClassCastException
    at java.lang.Class.cast(Unknown Source)
    at 
org.chromium.sdk.internal.protocolparser.dynamicimpl.JsonProtocolParser$SimpleCa
stParser.par
seValueQuick(JsonProtocolParser.java:627)
    ... 25 more

The problem is that Json response has name property value set to 0.

I cannot identify the exact cause of the problem. You can find json text in 
attachment.