Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.3.1f1
Issue ID
1056678
Regression
No
[Linux] [VSCode] Debugger doesn't attach to editor
To reproduce:
1) Open attached project
2) Open C# project with VSCode
3) Have Unity Debugger extension installed
4) In VSCode, select "Debug -> Start Debugging -> Unity Debugger"
5) Open Debug Tab
6) Add a breakpoint in DebugMe.cs at line 13
7) Try attaching debugger
It errors out with error:
spawn mono ENOENT
Reproduced in 2017.3.1f1, 2018.2.0b10
Not reproduced in Mac 10.13
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment