Join GitHub today
For macOS High Sierra, follow README.md for High Sierra. Consult this document for debugging and general tips. Consult this document for debugging and general tips. See the debugging section below and closed issues before opening a new issue. Visual Studio Code on macOS Installation. Download Visual Studio Code for macOS.; Double-click on the downloaded archive to expand the contents. Drag Visual Studio Code.app to the Applications folder, making it available in the Launchpad. Disk Utility has a hidden Debug menu that can list hidden volumes on drives attached to your Mac. Use this terminal command to enable the debug menu. Lifewire Enable Disk Utility's Debug Menu. Search the site GO. Tips & Tricks Basics Guides & Tutorials. Easy Steps to Partition Your Mac's Hard Drive with This Free Tool.
Terminal will display all of the partitions currently connected to your Mac. That's all there is to enabling or disabling the Disk Utility Debug menu. Go ahead and see what features are available under the Debug Menu, you will probably find the Show every partition item and the Force update of disk list item the most useful. Serial Port Terminal is a perfect tool to ease the routine of developers' everyday work. It features everything a professional developer needs for debugging, testing and troubleshooting serial.
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave 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
Comments
commented Mar 18, 2017
When trying to debug a MVC Web project in VS 2017 Mac I get the error message: Unable to attach to CoreCLR. dotnet
dotnet --info
|
commented Mar 20, 2017
Got the same issue (also on Sierrs 10.12.4 beta) |
added the area-Diagnostics label Mar 21, 2017
commented Mar 21, 2017
This will be fixed in the next 1.0 and 1.1 service releases and has been fixed in the master branch. |
commented Mar 28, 2017
When will it be available ? Thanks |
commented Mar 28, 2017 • edited
edited
Sierra 10.12.4 is now being pushed as an update by Apple. I installed the update this morning and now I can no longer debug in VS Code ('Unable to attach to CoreCLR.'). I believe this is the same issue reported above. I installed the latest .NET Core SDK ( dotnet --version now says 1.0.1 ). Is the fix available elsewhere, or any advice please? |
commented Mar 28, 2017
Here is a work around that worked for Gregg Miskelly:
|
commented Mar 28, 2017
Confirmed workaround works. Thanks for the info. When the real fix is released, will I need to 'reverse' the workaround, or will installing the new software get me back to consistency? |
commented Mar 29, 2017
Is there a workaround for Visual Studio Mac ? |
commented Mar 29, 2017
@gregg-miskelly Is there a workaround for VS for Mac? |
commented Mar 29, 2017
I don't have precise steps, but you can work around this by downloading https://vsdebugger.azureedge.net/coreclr-debug-1-9-0/coreclr-debug-osx.10.11-x64.zip, and replacing the version of vsdbg that VS for Mac is using with that version. @DavidKarlas do you have better instructions? |
commented Mar 29, 2017
This fixed it for me, in Visual Studio for Mac:
|
commented Mar 29, 2017
@suqram You just saved my day and night! Thx. |
commented Mar 29, 2017
@suqram it worked well! Thanks |
commented Mar 29, 2017
fix it for me! |
commented Mar 30, 2017
@suqram Excellent! Work for me! Thanks |
commented Mar 30, 2017
Excellent, copying the libdbgshim file as instructed by @suqram did the trick. |
commented Mar 31, 2017
@suqram Excellent! Work for me! Thanks |
commented Mar 31, 2017
Works for me too! thanks! |
commented Mar 31, 2017
@mikem8361 what does this mean? |
commented Mar 31, 2017
A nuget file is a zip file. Rename to .zip and run unzip on it. |
commented Apr 1, 2017
@suqram Work for me as well - thank you. |
commented Apr 1, 2017
@suqram Thanks so much! It works! |
commented Apr 1, 2017
Is this issue fixed in production now, or is it still in workaround? I noticed a new C# Extension and installed it yesterday. Does that contain the fix? |
commented Apr 3, 2017
@robbpriestley Sure seems like it. This is in the changelog for the extension in vs code: What's New in 1.8.1 Fixes debugging on macOS Sierra 10.12.4. (and it's working) Brilliant! |
commented Apr 3, 2017 • edited
edited
I did precisely what @suqram suggested, but now I get a popup when I try to run my application:
I don't get the 'Unable to attach to CoreCLR' message in my Application Output window anymore, so that's fixed. (and to clarify: when I run 'dotnet' or 'dotnet --info' , my results are identical to those from @AAimson) |
commented Apr 3, 2017
@joristt if you have the 1.8.1 extension installed and you are still running into an issue, your issue isn't related to this issue. Please open a new issue, this issue is long enough :). |
commented Apr 3, 2017
I was working on aspnet core when this issue started, and with VS preview it used to start a new Browser with a new debug session. Am i looking for the wrong setting now? |
![Snippet tool for mac Snippet tool for mac](/uploads/1/2/6/4/126452877/322601618.png)
commented Apr 3, 2017
@gregg-miskelly Yeah you're right, sorry :). You said
and I interpreted that as: replace only the vsdbg Unix executable. Tried copying everything from that zip to the VS Adapter directory 1 minute after commenting here and that fixed the problem. |
commented Apr 3, 2017
@robvdveer by 'VS Preview' you mean 'VS For Mac Preview' correct? If so - VS For Mac hasn't shipped an update vsdbg package containing the fix yet (at least to my knowledge), so you are very likely at the right place. There are two work arounds posted above, but I will give you the latest version of it --
|
commented Apr 3, 2017
Thanks @gregg-miskelly for such a quick response! |
commented Apr 4, 2017
@gregg-miskelly well played. Thanks |
commented Apr 5, 2017
@gregg-miskelly saved the day!!!! |
commented Nov 23, 2017
Online Debugging Tool
@gregg-miskelly this will work on the visual studio preview the debug gives an execution error |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
If you want to do a clean install of macOS Sierra, or you have multiple Macs to install it on, then a bootable flash drive for is your best bet for easy installation. Here’s how to make one.
The Easy Option: Disk Creator
The easiest way to create a USB flash installer is with the free program, Disk Creator.
Advertisement
- Download the macOS Sierra installer and Disk Creator.
- Insert an 8GB (or larger) flash drive. If you have any other data on that flash drive, back it up now, because the installer will delete everything on it.
- Open Disc Creator and click the “Select the OS X Installer” button.
- Find the Sierra installer file. This is should be located in your Applications folder.
- Select your flash drive from the drop-down menu.
- Click “Create Installer.”
When it’s done, insert your USB drive into any Mac, then launch the installer by holding down the Option key when you boot up your computer.
Advertisement
The DIY Option: Terminal
If you don’t want to download an extra bit of software, you can make your own installer USB drive using Terminal.
Snipping Tool For Mac
Advertisement
- Download the macOS Sierra installer.
- Insert an 8GB (or larger) flash drive and give it a name. For this tutorial, we’ll use the name
Untitled
. Make sure the drive is formatted for OS X Extended (Journaled). If it isn’t, open up Disk Utility and format is so it is. Before you do so, back up any important data on that drive. It’s best to disconnect any other external hard drives or flash drives so you don’t mix them up. - Open up Terminal (Applications > Utilities).
- Type (or copy and paste) this command into Terminal, replacing
Untitled
with the name of your drive, then press Enter:sudo /Applications/Install macOS Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install macOS Sierra.app --nointeraction &&say Done
- Type in your password when prompted and press Enter.
- Let the command line do its work and don’t interrupt it until you see the final line that says
Done
. This can take a while, so be patient.
Advertisement
Debugging Tool For Mac Sierra Terminal Commands
When it’s done, insert your USB drive into any Mac, then launch the installer by holding down the Option key when you boot up your computer.