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
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.