-
Notifications
You must be signed in to change notification settings - Fork 512
Debugger crashes when stepping-in #738
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
Comments
Hey Alex, thanks for the report! I can't see an obvious issue in the logs, could you possibly provide me with the simplest script that reproduces the issue so I can try to catch it in the debugger? |
Thanks, David. Is there an email address I can send the script to? To make sure you can run it, I have supplied read-only keys to an AWS account. I'd prefer not to post that here. In the meantime, I am attaching the logs for a test of the script I'd send you which crashed in vscode (but not in a macOS PowerShell console). Best, |
Yep! Send it along to |
Hi. My symptoms have changed! Now, when debugging a PowerShell script on macOS in vscode 1.13.1 and PowerShell module 1.4.1 on beta 3 of PowerShell six, the first couple of step-ins execute. Then everything just hangs. It's usually after an What could I attach to this problem to help debug this issue? It's really the same issue as it's been: something about the combo of vscode and module AWSPowerShell.NetCore and debugging is not working. Thanks. Alex |
Inadvertently closed by hitting the wrong button. ;-) |
System Details
$PSVersionTable
:PSVersion: 6.0.0-beta
PSEdition: Core
BuildVersion: 3.0.0.0
CLRVersion:
GitCommitId: v6.0.0-beta.1
OS: Darwin 16.5.0 Darwin Kernel Version 16.5.0: F...
Platform: Unix
PSCompatibleVersions: {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
WSManStackVersion: 3.0
Issue Description
I am experiencing a problem with...
debugging a script using module AWSPowerShell.NetCore. Script runs fine UNTIL it's debugged, at which point, a step-in will crash VS Code as shown in the attached screenshot
Attached Logs
Archive.zip
Image
The text was updated successfully, but these errors were encountered: