vscode-csharp icon indicating copy to clipboard operation
vscode-csharp copied to clipboard

Debugger doesn't support debugging x86 processes on x64 Windows

Open cwistedt opened this issue 8 years ago • 8 comments

Environment data

dotnet --info output: .NET Command Line Tools (1.0.4)

Product Information: Version: 1.0.4 Commit SHA-1 hash: af1e6684fd Runtime Environment: OS Name: Windows OS Version: 6.1.7601 OS Platform: Windows RID: win7-x64 Base Path: C:\Program Files\dotnet\sdk\1.0.4

VS Code version: 1.15.0

C# Extension version: 1.12.1

Steps to reproduce

  1. dotnet new mvc -o projname
  2. cd projname
  3. code . (start vscode)
  4. change <TargetFramework>netcoreapp1.1</TargetFramework> to <TargetFramework>net452</TargetFramework> in projname.csproj
  5. run: dotnet restore
  6. ctrl+shft+d (opens debug)
  7. Hit F5 (start debug) -> Choose .Net Core to create a launch.json
  8. In launch.json change to net452 and .dll to projname.exe
  9. Hit F5 again -> Click open Configure Task Runner -> Choose .Net Core
  10. In tasks.json Change "command": "dotnet build", -> "command": ""dotnet build '${workspaceRoot}/projname.csproj'"",
  11. Set a Breakpoint and Hit F5 again
  12. Popup showing "Only 64-bit processes can be debugged."

Expected behavior

Should start debugging and hit breakpoints

Actual behavior

Only shows the error message and stops

If i change the <TargetFramework> to netcoreapp1.1 in projname.csproj and in launch.json change to netcoreapp1.1 and .dll to projname.dll the debbuging works and the breakpoints are hit. I checked the projname.dll that netcoreapp1.1 produced and the projname.exe that the net452 produced. And they are both in x86.

Am i doing something wrong, have something installed incorrectly or is this the expected behaviour?

cwistedt avatar Aug 16 '17 12:08 cwistedt