Search Issue Tracker
Fixed in 4.3.X
Votes
0
Found in
4.3.0a4
Issue ID
557059
Regression
Yes
Conditional breakpoints are not working in MonoDevelop
1) What happened
Conditional breakpoints are not working in MonoDevelop
2) How can we reproduce it using the example you attached
Open Tests.cs in MonoDevelop
Place a breakpoint at "void Start()"
Change properties and set conditions
Attach to Unity process
Start the scene
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
TehWardy
Apr 29, 2016 20:07
Worth noting the same problem happens in VS2015 too.
And why when a debugger is attached does unity not stop on errors?
It simply reports them and carries running the broken code, all other C# projects I have ever built stop on error lines.
This issue and the "closed bug" we have here make some situations near impossible to debug.
TehWardy
Apr 29, 2016 20:04
This isn't fixed in unity v5.3.4f1 ... I have project where setting starting the project under these conditions simply causes unity to freeze up.
The only way to resolve the problem is to kill the unity editor process and reload.