-
Notifications
You must be signed in to change notification settings - Fork 676
Debugging Sandboxed Processes on OSX
Gregg Miskelly edited this page May 21, 2021
·
2 revisions
The debugger has basic support for attaching to processes that load CoreCLR in a sandbox. Note that this workflow is subject to change in the future.
To tell the debugger that your application is loaded in a sandbox, you need to drop a .json file next to your application's executable. It should have the same name as your application with an added .coreclr-debug-config.json
. The content of this file is as follows:
{
"applicationGroupId" : "<value-here>"
}
Notes:
- This will work in both Visual Studio and VS Code
- Comments are NOT supported
- The file must be UTF-8 encoded. A BOM is allowed but not required.
Configuration
- Configuring Snap installs of dotnet-sdk
- Configuring Arch Linux for Unity development
- Configuring Arch Linux for Razor development
- Installing the .NET Core Debugger on Arch Linux
Debugger
- Overview
- launch.json Help
- Feature List
- Enable Logging
- Portable PDBs
- Troubleshoot Breakpoints
- Attaching to remote processes
- Remote Debugging On Linux-Arm
- Windows Subsystem for Linux
- Diagnosting 'Debug adapter process has terminated unexpectedly'
- Testing libicu compatibility on Linux
- Debugging into the .NET Runtime itself
- Debugging x64 processes on an arm64 computer
Documentation
- Change Log
- Branches and Releases
- Installing Beta Releases
- Installing without internet connectivity
- Linux Support
- Run/Debug Unit Tests
- Troubleshooting: 'The .NET Core SDK cannot be located.' errors
Developer Guide