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

does not work on windows #12

Closed
smallnest opened this issue Apr 8, 2016 · 9 comments
Closed

does not work on windows #12

smallnest opened this issue Apr 8, 2016 · 9 comments

Comments

@smallnest
Copy link

My environment:

  1. windows 10
  2. atom 1.6.2
  3. installed delve and add delve in the path
  4. godebug 0.1.5

It shows go-debug has been installed in setting page but go-debug has not displayed in Pakcages menu.

And when I opened a main.go file, and press F5, there is no any debug panels.

@lloiser
Copy link
Owner

lloiser commented Apr 8, 2016

The panel should be visible after installing it... maybe something went wrong.
You can show/hide the panel using ctrl-k ctrl-g.

@lloiser
Copy link
Owner

lloiser commented Apr 8, 2016

But it seems to be a nice feature to show the panel whenever you start delve (using F5 for debug or ctrl-F5 for test)

@smallnest
Copy link
Author

It shows go-debug has not started and it exited:

consumeGoconfig (service) {
    goconfig = service;
    goconfig.locator.findTool("dlv").then((p) => {
        path = p;
        this.start();
    });
},

start() {
    if (!dependenciesInstalled || !path) {
        alert("hello")
        return;
    }

I

@lloiser
Copy link
Owner

lloiser commented Apr 8, 2016

go-debug depends on two things in the beginning:

once both are done the panel should start.

So either the dependencies failed (which should log something into the console) or go-config couldn't find delve...

@smallnest
Copy link
Author

Thanks. The two passes and I found the below debug alert has not been triggered.

panel = require("./panel.jsx");
alert("hello")

I need to investigate it more but I am not familiar with node.js.

I can't found any logs in logs (I can't find any log file except SquirrelSetup.log)

@lloiser
Copy link
Owner

lloiser commented Apr 8, 2016

I don't write any log files. Open the developer tools in atom (alt-cmd-i / alt-ctrl-i) and check the console. Do you see any logs there?

@smallnest
Copy link
Author

Yes, Thanks. The log is:

TypeError: Cannot read property 'Component' of undefined(…)
Uncaught (in promise) TypeError: Cannot read property 'Component' of undefined
    at Object.<anonymous> (C:\Users\smallnest\.atom\packages\go-debug\lib\variables.jsx:64:23)
    at Module._compile (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\native-compile-cache.js:50:27)
    at Object.<anonymous> (C:\Users\smallnest\.atom\packages\go-debug\lib\panel.jsx:25:21)
    at Module._compile (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\native-compile-cache.js:50:27)
    at Object.start (C:/Users/smallnest/.atom/packages/go-debug/lib/main.js:60:11)
    at C:/Users/smallnest/.atom/packages/go-debug/lib/main.js:42:9
    at process._tickCallback (node.js:368:9)

and

Error reading compiled file TypeError: Cannot read property 'getCachePath' of undefined
    at require.install.retrieveSourceMap (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\compile-cache.js:130:51)
    at mapSourcePosition (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\node_modules\source-map-support\source-map-support.js:140:21)
    at wrapCallSite (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\node_modules\source-map-support\source-map-support.js:303:20)
    at C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\node_modules\source-map-support\source-map-support.js:338:26
    at Array.map (native)
    at prepareStackTrace (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\node_modules\source-map-support\source-map-support.js:337:24)
    at Function.prepareStackTraceWithRawStackAssignment (C:\Users\smallnest\AppData\Local\atom\app-1.6.2\resources\app.asar\src\compile-cache.js:174:12)
    at Object.InjectedScript._describe (<anonymous>:1213:32)
    at InjectedScript.RemoteObject (<anonymous>:1298:39)
    at Object.InjectedScript._wrapObject (<anonymous>:381:20)
    at Object.InjectedScript.wrapObject (<anonymous>:298:25)

@lloiser
Copy link
Owner

lloiser commented Apr 8, 2016

see #8

@smallnest
Copy link
Author

Thanks a lot.

The reason is same to #3. Disable hyperclick and go-debug works well.

The "hyperclick" package has been superseded by the "nuclide" package. If you'd like to use Hyperclick, install the "nuclide" package and disable the features you don't need.

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

2 participants