-
I have created initial version of [j2v8-debugger](https://github.com/AlexTrotsenko/j2v8-debugger) using _Stetho_ for communication with _Chrome DevTools_ as it was sugessted in #293.
Definitely cu…
-
```
SDK/Debugger version: 0.3.8.201210040400
Eclipse version:3.7.2
Google Chrome/V8 Embedder + version: 29.0.1547.66 m
[For WebKit (WIP) protocol] Backend version:WK@120709
OS + version: Windows 7 SP1…
-
```
SDK/Debugger version: 0.3.8.201210040400
Eclipse version:3.7.2
Google Chrome/V8 Embedder + version: 29.0.1547.66 m
[For WebKit (WIP) protocol] Backend version:WK@120709
OS + version: Windows 7 SP1…
-
```
SDK/Debugger version: 0.3.8.201210040400
Eclipse version:3.7.2
Google Chrome/V8 Embedder + version: 29.0.1547.66 m
[For WebKit (WIP) protocol] Backend version:WK@120709
OS + version: Windows 7 SP1…
-
Following #10, there seems to be an issue with how `!DEBUG` line are called.
```
> chrome
cderv updated
5 years ago
-
## Summary & Context
When technicians try to run any protocols in Aquarium, this error appears instead of the interactive protocol screens.
 protocol] Backend version:WK@120709
OS + version: Windows 7 SP1…
-
```
SDK/Debugger version: 0.3.8.201210040400
Eclipse version:3.7.2
Google Chrome/V8 Embedder + version: 29.0.1547.66 m
[For WebKit (WIP) protocol] Backend version:WK@120709
OS + version: Windows 7 SP1…
-
```
SDK/Debugger version: 0.3.8.201210040400
Eclipse version:3.7.2
Google Chrome/V8 Embedder + version: 29.0.1547.66 m
[For WebKit (WIP) protocol] Backend version:WK@120709
OS + version: Windows 7 SP1…