Debugging not working with XCode 12 selected #42311

DavidKarlas · 2020-09-16T12:32:17Z

Description

In VSMac, we are using vsdbg(same as Omnisharp) to debug .NET Core applications... We have unit tests, but ever since bumping XCode from 11 to 12, debugging started failing... So here are repro steps:

sudo xcode-select -s /Applications/Xcode_12.app
mkdir xcodeTestProj
cd xcodeTestProj
dotnet new console
dotnet publish --runtime osx-x64
code .
create launch.json via VSCode, and change:

"program": "${workspaceFolder}/bin/Debug/net5.0/xcodeTestProj.dll",
to
"program": "${workspaceFolder}/bin/Debug/net5.0/osx-x64/publish/xcodeTestProj.dll",

Start debugging
Observe Debug Console print Unable to attach to CoreCLR. Unknown Error: 0x80131c3c

Now try all steps, but change step 1 to sudo xcode-select -s /Applications/Xcode_11.app(notice change of Xcode version), it will work fine.

I tried to change to not use published version... But when tests are executing they fail either wrong variables values are reported or “Unable to evaluate expression because the code is optimized o...”.(Only when using XCode 12, fine with XCode 11). I believe underlining problem is same, hence I suggest trying debugging published app since its easier repro...

Im not sure how is selecting XCode 12 vs 11 effecting debugging of CoreCLR, but it does, I suspect its something related to lldb or some libraries used...

Configuration

Which version of .NET is the code running on? 3.1, but also tried with 5.0
What OS and version, and what distro if applicable? macOs
What is the architecture (x64, x86, ARM, ARM64)? x64
Do you know whether it is specific to that configuration? Yes(macOs)
If you're using Blazor, which web browser(s) do you see this issue in? N/A

Regression?

No.

Other information

We have to disable .NET Core unit tests for until this is resolved, but I also believe this will effect users when doing some complex debugging.

The text was updated successfully, but these errors were encountered:

ghost · 2020-09-16T12:32:21Z

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

tommcdon · 2020-09-16T16:26:45Z

@hoyosjs
FYI @caslan

mrward · 2020-09-18T16:52:46Z

Looks like we may be seeing some customers running into this problem when debugging in VS Mac with Xcode 12 installed.

https://developercommunity.visualstudio.com/content/problem/1190334/unable-to-attach-to-coreclr-unknown-error-0x80131c.html - Xcode 12 being used here.
https://developercommunity.visualstudio.com/content/problem/1189274/unable-to-debug-azure-function-locally-on-mac.html - Not confirmed Xcode 12 use here.

c-lamont · 2020-09-19T09:14:00Z

I can confirm this workaround.

Download Xcode 11: https://download.developer.apple.com/Developer_Tools/Xcode_11.7/Xcode_11.7.xip
Unzip and rename to Xcode_11
Move it to your Applications folder
Open terminal
Go to root: cd /
Run: sudo xcode-select -s /Applications/Xcode_11.app

Now everything works for me.

brminnick · 2020-09-19T15:07:35Z

Thanks!

Download Xcode

The direct link to the Xcode 11.7 file didn't work for me.

In case anyone else is having trouble, go to Apple's More Downloads for Apple Developers page and search Xcode 11.7 👍

DavidKarlas · 2020-09-23T12:47:02Z

Hi @tommcdon @hoyosjs,

Im wonder how could priority on this be increased so someone takes a look at this since more and more developers will start switching to XCode 12 since it was released last week, and milestone .NET 6 feels too far away... At first I though this would only be problem for unit tests but looks like its effecting also developers...

Regards,
David

borzuyehr · 2020-09-23T19:49:33Z

@c-lamont and @brminnick solution worked for me as a workaround as well. Just to mention, my initial workaround was to Dockerize my .NET core app and run it in a Linux container. Just in case the above workaround does not work for others out there.

hoyosjs · 2020-09-23T20:07:35Z

@DavidKarlas the milestone means that it will be completed in master first. If there's enough customer feedback, we take it to ship room for backport approval. I can imagine this fitting the requirements easily.

And sorry for the time it's taken me. I've had an avalanche of issues coming in and I tried getting XCode 12, but my Mac seems... a little hesitant to help here. With all of us working from home, I haven't been able to access a different device. I'll see if a teammate can help me out to repro this.

DavidKarlas · 2020-09-24T05:27:48Z

@hoyosjs Tnx for explaining, I just thought that milestone means it will have to wait few months... If you want me to do some testing/debugging let me know.

mklement0 · 2020-09-29T13:51:02Z

Re workaround:

It seems that downloading and installing the "Command Line Developer Tools for Xcode 11.5" (*.dmg, contains an installer package (*.pkg), about 260MB) from https://developer.apple.com/download/more/ is sufficient (no need for Xcode 11 as a whole).

Once installed, switch to this version of the tools with sudo xcode-select -s /Library/Developer/CommandLineTools

ftntming · 2020-10-16T04:44:54Z

Re workaround:

It seems that downloading and installing the "Command Line Developer Tools for Xcode 11.5" (*.dmg, contains an installer package (*.pkg), about 260MB) from https://developer.apple.com/download/more/ is sufficient (no need for Xcode 11 as a whole).

Once installed, switch to this version of the tools with sudo xcode-select -s /Library/Developer/CommandLineTools

Works like a charm in OSX 10.15.7, VS Studio 2019

MisterJimson · 2020-10-16T15:15:01Z

Re workaround:

It seems that downloading and installing the "Command Line Developer Tools for Xcode 11.5" (*.dmg, contains an installer package (*.pkg), about 260MB) from https://developer.apple.com/download/more/ is sufficient (no need for Xcode 11 as a whole).

Once installed, switch to this version of the tools with sudo xcode-select -s /Library/Developer/CommandLineTools

Also fixes the issue on Rider for me as well.

hoyosjs · 2020-10-19T18:06:28Z

This is most likely fixed by #42900

icelated · 2020-11-04T23:40:31Z

I upgraded Xcode to the new version 12.1 and now the debugger is busted. Not to mention in the simulator the perform segue goes to the view controller but the view doesn't render. Worked before the update and works on my phone. Also, the date picker is coming up different in the simulator.

kuromukira · 2020-11-11T03:54:01Z

Hi, I'm experiencing this bug since I updated my XCode to 12 (now 12.1). Would it affect my mobile app builds if I install the build tools for XCode 11? It's frustrating to not be able to debug code in Rider and Visual Studio.

hoyosjs · 2020-11-11T04:20:05Z

Hi, I'm experiencing this bug since I updated my XCode to 12 (now 12.1). Would it affect my mobile app builds if I install the build tools for XCode 11? It's frustrating to not be able to debug code in Rider and Visual Studio.

This is related to the tools that are installed on the machine that's running the app under the debugger. We used to rely on vmmap, which was updated in a way that broke our usage. It's only used in debugging scenarios. There was a contribution to fix this for .NET 6 (master), but it needs to be ported to other releases. As I get feedback of it affecting users I can justify getting it backported.

cc: @gregg-miskelly the affected API needed for this lives in the PAL and is only really used through dbgshim (apis like CreateVersionStringFromModule and EnumerateCLRs).
cc: @tommcdon

kuromukira · 2020-11-11T05:24:31Z

Thanks @hoyosjs . It's manageable for the meantime debugging code only through Console.WriteLine. As long Running without Debugging doesn't break anytime soon.

But it would really be great to have this fixed and be able to debug code normally again.

MisterJimson · 2020-11-11T12:45:57Z

@kuromukira you can use the workarounds posted above to debug normally. Using an older copy of Xcode. Its pretty easy to switch back and forth if you also do other things with Xcode 12.

8or15 · 2020-11-14T10:53:16Z

@hoyosjs after upgrading to Big Sur I'm unable to use the workaround, so a back port of the fix would be helpful.

stevo-knievo · 2020-11-15T22:27:29Z

I have the same issue as @8or15.

Here the error if you try to install the Command Line Tools 11.5:
Command Line Tools 11.5 can't be installed on the disk. The version of macOS is too new.

@hoyosjs
Please back port the fix to .NET Core 3 and .NET 5.

- .NET Core SDK 3.1.404 (Commit: 470f6754b3)
- macOS: 11.0.1 (20B29) - Darwin 20.1.0
- Xcode
    Version:	12.2 (12B45b)
    Xcode:	12.2 (17535)
    Instruments:	12.2 (64541.11)
- CommandLineToolsForXcode: 2384 (via xcode-select --version)

wingchunninja · 2020-11-16T15:52:15Z

I was experiencing the same issue before and the fix did it for me. But after updating to BigSur
and with Visual Studio Version 1.51.1 doesn't work anymore. Anybody else experiencing this?
And also the same issue when trying to install Command Line Tools 11.5.

stevo-knievo · 2020-11-16T16:45:34Z

I had to downgrade back to macOS Catalina 10.15.7 (19H2) and the Command Line Developer Tools for Xcode 11.5 (version 2373). Currently, that is the only way I can be productive on .NET Core 3.1

hoyosjs · 2020-11-16T22:24:47Z

@mikem8361 has started the discussions for the backport in #44748

mii9000 · 2020-11-28T08:45:39Z

None of the solutions work for me on Big Sur 😢

hoyosjs · 2020-11-29T02:24:52Z

The fix had been merged in time to make it into our next official build. After that it needs to be picked up by the different debuggers in the ecosystem. VS for mac and VSCode use the same debugger engine and the owners expressed interest in including the fix as soon as possible.

sdmaclea · 2020-12-01T18:58:57Z

@hoyosjs Looks like it was backported to .NET 5. Does the issue affect .NET 2.1 and/or .NET 3.1? Are those backports being requested too?

gregg-miskelly · 2020-12-01T19:08:12Z

@sdmaclea Because this is a dbgshim fix - it doesn't need to be. Any debugger that wants this fix can use the .NET 5 dbgshim.

mrward · 2020-12-04T15:48:49Z

Ran a test of this fix and it looks good to me with Xcode 12.2.

Installed .NET 5.0.1
Ran David's repro steps.
Debugger fails
Copied the dylib from .net 5.0.1 from /usr/local/share/dotnet/shared/Microsoft.NETCore.App/5.0.1/libdbgshim.dylib to ~/.vscode/extensions/ms-dotnettools.csharp-1.23.6/.debugger
Restarted VS Code and then debugged the project again
- the debugger runs and breakpoints can be hit in the console project.

I am assuming there will be a more official debugger zip at some point with this updated libdbgshim.dylib that can be bundled with OmniSharp and VS Mac?

mrward · 2020-12-04T16:46:45Z

@wingchunninja Sorry, I was testing an internal 5.0.1 build. Not sure if this change has made it into the 5.0.200 preview builds from https://github.com/dotnet/installer yet.

wingchunninja · 2020-12-04T16:50:18Z

@mrward Ah okay. Thank you. I will take a look if there are some changes there. It is a pretty blocking issue for me since i cannot debug in the normal way without console logging.

gregg-miskelly · 2020-12-04T17:20:19Z

I am assuming there will be a more official debugger zip at some point with this updated libdbgshim.dylib that can be bundled with OmniSharp and VS Mac?

Yes, soon after 5.0.1 ships the VS debugger team expects to put out a new release of vsdbg-ui which can be included into the VS Code C# extension and VS For Mac.

wingchunninja · 2020-12-04T17:33:14Z

@wingchunninja Sorry, I was testing an internal 5.0.1 build. Not sure if this change has made it into the 5.0.200 preview builds from https://github.com/dotnet/installer yet.

@mrward Thank you for the hint. This did the work for me 🙂

hoyosjs · 2020-12-08T10:31:24Z

@tommcdon set this to tracking as all the runtime side of the work is done.

gregg-miskelly · 2020-12-09T17:24:15Z

There is now a beta release of the VS Code C# extension that contains this fix: v1.23.8-beta1.

kuromukira · 2020-12-09T23:05:54Z

@gregg-miskelly How about for VS for Mac? Still can't debug with VS for Mac even with 5.0.1 installed

mrward · 2020-12-10T09:40:10Z

@kuromukira There should be a new VS Mac 8.8.4 release with the updated debugger at some point - I do not have a specific date as yet.

For a workaround you can probably copy the libdbgshim.dylib from /usr/local/share/dotnet/shared/Microsoft.NETCore.App/5.0.1/libdbgshim.dylib into VS Mac's app bundle /Applications/Visual\ Studio.app/Contents/Resources/lib/monodevelop/AddIns/DotNetCore.Debugger/Adapter/libdbgshim.dylib - making a backup copy of this file in the Adapter directory so you can rollback if it breaks something.

joshardt · 2020-12-17T08:21:26Z

VS4M version 8.8.4.30 which contains a fix for this issue is available by now: https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2019-mac-relnotes#884

Issue can probably get closed.

DavidKarlas · 2020-12-17T08:33:54Z

Looking at VSCode extension, looks like they have fix available in preview and will probably land very soon on stable, closing.

Dotnet-GitSync-Bot added area-Diagnostics-coreclr untriaged New issue has not been triaged by the area owner labels Sep 16, 2020

tommcdon removed the untriaged New issue has not been triaged by the area owner label Sep 16, 2020

tommcdon added this to the 6.0.0 milestone Sep 16, 2020

marek-safar added the os-mac-os-x macOS aka OSX label Sep 19, 2020

hoyosjs linked a pull request Nov 16, 2020 that will close this issue

[release/5.0] Get modules information using proc_pidinfo() on macOS #44748

Merged

hoyosjs mentioned this issue Nov 29, 2020

Unable to debug .NET 5 application after upgrading to macOS Big Sur #45282

Closed

hoyosjs added the tracking This issue is tracking the completion of other related issues. label Dec 8, 2020

hoyosjs modified the milestones: 6.0.0, Future Dec 8, 2020

gregg-miskelly mentioned this issue Dec 9, 2020

Update debugger to 1.23.8 dotnet/vscode-csharp#4281

Merged

DavidKarlas closed this as completed Dec 17, 2020

This was referenced Dec 18, 2020

Mac m1 debugger won't start on aspnet core projects, program has exited #46226

Closed

dotnet crash when debugging unit tests on Visual Studio for Mac (Rosetta) #46192

Closed

ghost locked as resolved and limited conversation to collaborators Jan 16, 2021

Debugging not working with XCode 12 selected #42311

Debugging not working with XCode 12 selected #42311

Comments

DavidKarlas commented Sep 16, 2020

Description

Configuration

Regression?

Other information

ghost commented Sep 16, 2020

tommcdon commented Sep 16, 2020

mrward commented Sep 18, 2020

c-lamont commented Sep 19, 2020

brminnick commented Sep 19, 2020 • edited Loading

DavidKarlas commented Sep 23, 2020

borzuyehr commented Sep 23, 2020

hoyosjs commented Sep 23, 2020 • edited Loading

DavidKarlas commented Sep 24, 2020

mklement0 commented Sep 29, 2020 • edited Loading

ftntming commented Oct 16, 2020

MisterJimson commented Oct 16, 2020

hoyosjs commented Oct 19, 2020

icelated commented Nov 4, 2020

kuromukira commented Nov 11, 2020

hoyosjs commented Nov 11, 2020 • edited Loading

kuromukira commented Nov 11, 2020

MisterJimson commented Nov 11, 2020

8or15 commented Nov 14, 2020

stevo-knievo commented Nov 15, 2020

wingchunninja commented Nov 16, 2020

stevo-knievo commented Nov 16, 2020

hoyosjs commented Nov 16, 2020 • edited Loading

mii9000 commented Nov 28, 2020

hoyosjs commented Nov 29, 2020

sdmaclea commented Dec 1, 2020

gregg-miskelly commented Dec 1, 2020

mrward commented Dec 4, 2020

mrward commented Dec 4, 2020

wingchunninja commented Dec 4, 2020

gregg-miskelly commented Dec 4, 2020

wingchunninja commented Dec 4, 2020

hoyosjs commented Dec 8, 2020

gregg-miskelly commented Dec 9, 2020

kuromukira commented Dec 9, 2020 • edited Loading

mrward commented Dec 10, 2020

joshardt commented Dec 17, 2020 • edited Loading

DavidKarlas commented Dec 17, 2020

brminnick commented Sep 19, 2020 •

edited

Loading

hoyosjs commented Sep 23, 2020 •

edited

Loading

mklement0 commented Sep 29, 2020 •

edited

Loading

hoyosjs commented Nov 11, 2020 •

edited

Loading

hoyosjs commented Nov 16, 2020 •

edited

Loading

kuromukira commented Dec 9, 2020 •

edited

Loading

joshardt commented Dec 17, 2020 •

edited

Loading