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

Failed to read variables #186

Open
KyleJune opened this issue Jan 25, 2015 · 3 comments
Open

Failed to read variables #186

KyleJune opened this issue Jan 25, 2015 · 3 comments

Comments

@KyleJune
Copy link

I recently installed Nodeclipse and have been having an issue. When in debug mode it always says "Failed to read variables" in the Variables window. I've tried it with different scripts and it always does that. The only work around I've been able to find is using the Expressions window because I'm able to type in the variable name there to view it still. However, it's a bit annoying to have to type in all the variable names into the Expressions window to view them. Below is a screen capture of the problem occurring, along with the code that is being debugged as a node application.

var a = 5;
var abc = 6;
var http = require('http');

image

@paulvi
Copy link
Member

paulvi commented Jan 26, 2015

Thank you for raising.

The debugger is from former Google ChromeDevTools.

I had similar issue before, but was not sure if it was only mine problem.
The quick fix can be to bring Expression View to front by default.

For bigger improvements, I guess nobody has time.

@paulvi paulvi added the bug label Jan 26, 2015
@cfonze
Copy link

cfonze commented May 5, 2015

How does one apply the quick fix?

@paulvi
Copy link
Member

paulvi commented Jan 11, 2018

That fix would have been having Expression View activated by default.

For users, just click Expression tab.

HELP WANTED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants