Skip to content

Debugger stopped working after upgrading vscode to 1.0 #149

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

Closed
ftischhauser opened this issue Apr 18, 2016 · 7 comments
Closed

Debugger stopped working after upgrading vscode to 1.0 #149

ftischhauser opened this issue Apr 18, 2016 · 7 comments
Labels
Issue-Bug A bug to squash.
Milestone

Comments

@ftischhauser
Copy link

ftischhauser commented Apr 18, 2016

Hi everyone

As the title says, my previously working setup suddenly stopped doing anything after the upgrade. I can see the the Microsoft.PowerShell.EditorServices.Host.exe process running in the background, but the GUI just waits forever for any output. Unfortunately I can't find any error messages in the log files which makes this very hard to track. Could anyone point me into the right direction? Thanks!

@daviwil
Copy link
Contributor

daviwil commented Apr 18, 2016

Hey Flavio, 1.0 appears to have changed some things that might have broken our debug adapter. Thanks for sending along the logs!

@daviwil
Copy link
Contributor

daviwil commented Apr 18, 2016

Another hit: microsoft/vscode#5429

@rkeithhill
Copy link
Contributor

BTW the updated debug protocol for 1.0.0 says this:

  • adapters sends InitializedEvent (after the InitializeRequest has returned)

We may need to merge that ordering change PR to a 0.5.1 branch and post it.

@jackmusick
Copy link

I believe I have the same issue. When starting the debugger, nothing happens. However, if I set a breakpoint, everything runs as expected.

@daviwil
Copy link
Contributor

daviwil commented Apr 27, 2016

Sorry for the trouble guys, we'll get a new update out to fix this in the next few days.

@daviwil
Copy link
Contributor

daviwil commented May 11, 2016

This is verified to be fixed in the 0.6.0 version of the extension, coming out very soon. I'll close this bug once the update has been shipped. Thanks for your patience!

@daviwil daviwil removed the Needs: Fix Verification Please verify the fix for us! label May 11, 2016
@daviwil
Copy link
Contributor

daviwil commented May 13, 2016

0.6.0 is now released! Let me know if you run into any further trouble.

@daviwil daviwil closed this as completed May 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

4 participants