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

Symbols cannot be loaded when debugging MSBuild task run from dotnet.exe #2903

Closed
jonathanbyrne opened this issue Sep 2, 2017 · 3 comments
Closed

Comments

@jonathanbyrne
Copy link

Steps to reproduce

  1. Extract attached zip file (MyTask.zip)
  2. Open MyTask.sln in Visual Studio 2017
  3. Ensure that the Just-In-Time debugger is enabled for Visual Studio 2017
  4. Execute "test-with-dotnet-build.bat" or "test-with-dotnet-msbuild.bat"
  5. Choose Visual Studio instance with MyTask solution to debug dotnet.exe

dotnet msbuild task debug screenshot 1

Expected behavior

The debugger should load the symbols for MyTask and allow debugging. Executing "test-with-msbuild.bat" will demonstrated the expected behavior.
dotnet msbuild task debug screenshot 2

Actual behavior

Visual Studio does not load the symbols for MyTask. The modules window states:

The module did not load at the default load address.

dotnet msbuild task debug screenshot 3

When choosing "Symbol Load Information..." from the module context menu, a dialog box states:

This module is a pre-compiled binary created by the ngen.exe tool. The debugger does not attempt to load symbols for these binaries, but will instead load symbols for original dll/exe when it is loaded by the .NET Runtime.

dotnet msbuild task debug screenshot 4

Environment data

Visual Studio Professional 15.4.0 Preview 1.0
MSBuild 15.3.409.57025
Dotnet 2.0.0
NuGet 4.3.0.4406

@jonathanbyrne jonathanbyrne changed the title Debugging MSBuild task run from dotnet.exe Symbols cannot be loaded when debugging MSBuild task run from dotnet.exe Sep 2, 2017
@steveharter
Copy link
Member

@dagood any comments? Thanks

@dagood
Copy link
Member

dagood commented Jan 10, 2018

It looks like this is the same issue as https://github.com/dotnet/coreclr/issues/12074: "Debugger.Launch doesn't work correctly on coreclr on Windows"

@steveharter
Copy link
Member

OK closing as dup

@msftgits msftgits transferred this issue from dotnet/core-setup Jan 30, 2020
@msftbot msftbot bot locked as resolved and limited conversation to collaborators Dec 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants