.NET 9 x64 on arm mac unable to debug

[Sh18RW]

Describe the bug

I am unable to start debugging anything using x64 .NET 9. I have tried using Visual Studio Code vsdbg and Rider, but the debugger starts and then suddenly stops without any message. In the Debug Console, I found similar error messages:
Rider:

Loaded application domain 'DefaultDomain (id 1)'
Loaded Assembly '/usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App/9.0.1/System.Private.CoreLib.dll'
Loading module /usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App/9.0.1/System.Private.CoreLib.dll in application domain 1:DefaultDomain
Pdb file for assembly /usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App/9.0.1/System.Private.CoreLib.dll was not found or failed to read
Started Thread 8414135

VS Code:

------------------------------------------------------------------------------
You may only use the Microsoft Visual Studio .NET/C/C++ Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software to help you
develop and test your applications.
------------------------------------------------------------------------------
Content.Client.dll (91023): Loaded '/usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App/9.0.1/System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[91023] Content.Client.dll' has exited with code 0 (0x0).

There is no any information.

To Reproduce

I use Mac Sonoma 14.4.1 with ARM archetype, x64 .NET 9.
If I use ARM version, it works fine.

Further technical details

$ dotnet --info
.NET SDK:
 Version:           9.0.102
 Commit:            cb83cd4923
 Workload version:  9.0.100-manifests.7c7c79ca
 MSBuild version:   17.12.18+ed8c6aec5

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  14.4
 OS Platform: Darwin
 RID:         osx-x64
 Base Path:   /usr/local/share/dotnet/x64/sdk/9.0.102/

.NET workloads installed:
There are no installed workloads to display.
Configured to use loose manifests when installing new manifests.

Host:
  Version:      9.0.1
  Architecture: x64
  Commit:       c8acea2262

.NET SDKs installed:
  8.0.405 [/usr/local/share/dotnet/x64/sdk]
  9.0.100-preview.1.24101.2 [/usr/local/share/dotnet/x64/sdk]
  9.0.102 [/usr/local/share/dotnet/x64/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.12 [/usr/local/share/dotnet/x64/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.0-preview.1.24081.5 [/usr/local/share/dotnet/x64/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.1 [/usr/local/share/dotnet/x64/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.12 [/usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.0-preview.1.24080.9 [/usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.1 [/usr/local/share/dotnet/x64/shared/Microsoft.NETCore.App]

Other architectures found:
  arm64 [/usr/local/share/dotnet]
    registered at [/etc/dotnet/install_location_arm64]

Environment variables:
  DOTNET_ROOT_ARM   [/usr/local/share/dotnet]
  DOTNET_ROOT_X64   [/usr/local/share/dotnet/x64]

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[tumetus]

I'm experiencing the same issue.
Sonoma 14.4.1, Apple M1 Max.

[marcpopMSFT]

@tommcdon is this your area?

[tommcdon]

@tommcdon is this your area?

Yes, thanks

[tommcdon]

@hoyosjs @mikem8361

[tommcdon]

@Sh18RW I was unable to reproduce the issue on my Mac m1 with Sequoia 15.3.1. Would you mind trying the instructions at https://github.com/dotnet/vscode-csharp/wiki/Debugging-x64-processes-on-an-arm64-computer and determine if the issue still reproduces?

[Sh18RW]

The issue is no longer reproducible now. It has been resolved. Apparently, some OS component has been updated.
Thanks.

[tommcdon]

Thanks @Sh18RW! I will close this issue since the issue no longer reproduces, as it was likely addressed by an OS/Rosetta fix.