Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.0f3
Issue ID
859744
Regression
Yes
Breakpoints do not trigger in monodevelop
To reproduce:
1) Create a script with the following code. Note the Debug.Log is commented out.
```
using UnityEngine;
public class TestScript : MonoBehaviour {
void Start () {
// Debug.Log ("Start"); // breakpoint here
}
}
```
2) Place a breakpoint on the commented line. It will automatically move to the next line, that is expected. Attach MonoDevelop to the Editor.
3) Enter playmode in the Editor. The debugger will stop at the end of the Start function.
4) Press the continue button in MonoDevelop. Don't switch to Unity just yet.
5) Uncomment the commented line. Save your changes.
6) Switch back to Unity
7) Wait for script to recompile
8) Switch back to monodevelop
9) Place breakpoint on uncommented line
10) Switch back to Unity. Stop and play scene again
11) Notice that breakpoint isn't triggered
12) Try to place breakpoint on Start method. Circles with transparent middle part appears next to line and error is thrown.
Reproducible with 5.5.0f3, 5.5.0p1, 5.5.0p4
Not reproducible with 5.4.3p4, 5.6.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Add comment