On 26 сен, 23:44, Robert Schultz <[email protected]> wrote:
> However I'd like to enhance the plugin, so I'm trying to get the
> plugin working in 'debug' mode after running from Eclipse.
(It might be interesting to know what exactly you would wish to
enhance in plugins)
> I've got all the chromedevtools Eclipse plugin code all checked out.
> All 8 plugin and feature projects are in my eclipse workspace, all
> built with no errors.
I think it's important for us to know which SNV revision you are
working with and which version of Eclipse you are running as your
target platform.
> I open up the org.chromium.debug.ui/plugin.xml and choose to 'Launch
> an Eclipse application in Debug mode'
> I modify the launch configuration to include all the .debug plugins
> including core.
It's a bit unfamiliar wording for me. Usually I don't start in UI with
a particular plugin, but simply open "Run -> Debug configuration" and
create "Eclipse Application" configuration their which includes all
plugins in Workspace by default.
However, probably it doesn't matter.
> When I launch the debug Eclipse, I correctly see the 'Chromium
> JavaScript' launch group.
> I'm able to create a launch configuration (the 'Remote Scripts Project
> Name' box is missing)
It is missing because our update site is slightly not up-to-date. It's
probably going to become in-sync again with our announcing standalone
V8 VM debug support. And we dropped project name field from UI.
> Any breakpoints in the plugin Java code in my other workspace are
> correctly hit so that part is working fine.
>
> When it lauches the chromiun javascript code though I get the
> following error:
> Unable to open perspectives as specified by launch: <unknown>
>
> Reason:
> Launch configuration chromedevtools-logger at file:/mnt/compendium/
> DevLab/runtime-EclipseApplication/.metadata/.plugins/
> org.eclipse.debug.core/.launches/chromedevtools-logger.launch does not
> exist.
That's bad. We are creating auxiliary launch configuration file for
running Console you are describing below. From your error message I
see it was looking for this file in a wrong directory. It might depend
on version of Eclipse. I need your version to check this.
Probably Eclipse provides a stacktrace for this error (viewable via
Erorr Log view: Window->Show View->Other => General->Error Log).
Without it I can't tell for sure but probably this exception
terminates debug session being started.
> I then get some items in my Console log:> Sent to Chrome:
>
> ChromeDevToolsHandshake
>
> > Received from Chrome:
>
> ChromeDevToolsHandshake
>
> > Sent to Chrome:
>
> Tool:DevToolsService
> Content-Length:21
>
> {"command":"version"}> Received from Chrome:
>
> Destination:
> Tool:DevToolsService
> Content-Length:45
>
> {"command":"version","data":"0.1","result":0}
>
> But then another error pops up:
> Failed to connect to the remote browser
> Failed to get protocol version from remote
This might be because the first problem threw an exception which
terminated debug session. In this case error message is inaccurate.
The other possibility is that some thread is blocked by exception in
Java debugger. It may lead to other thread giving up waiting for
version respond and the error message. However, I would exception
"timeout" somewhere in error message in this case.
Peter
--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---
