How do I step into my code when automatic Pause mode in Unity occurs?

Question

In my scripts, I have several "Debug.Break();".

I use them to halt the execution of the script when unexpected situations occur, for example like here:

 if (condition == 1) 
 {
    DoThis();
 }
 else if (condition == 2)
 {
    DoThat();
 }
 else
 {
     //this should not happen! Check what goes on here
     Debug.Break();
 }

When my game hits such a "Debug.Break()", the gameplay is automatically paused.

It looks like this:

Ideally, I would have the Debugger attached, and I would have a breakpoint set, then Visual Studio would show me exactely where it stopped.

It would look like this:

However, I don't have breakpoints at all Debug.Break(); and sometimes I do not even have the Debugger attached to Unity.

It would look like that:

How could I anyways still step into the line where Unity halted? I would like to see where exactely Unity halted, but I don't see how.

Do I always have to have breakpoints set and the Debugger attached? Or could I still attach the debugger later and still step into where the script halted?

The reason why I don't have the Debugger attached at all time is that I frequently change the scripts, then I need to save it and detach and re-attach the Debugger. This is too time-taking.

I am using Visual Studio Community Edition.

Answer 1

How could I anyways still step into the line where Unity halted? I would like to see where exactely Unity halted, but I don't see how.

Do I always have to have breakpoints set and the Debugger attached?

Yes.

The reason why I don't have the Debugger attached at all time is that I frequently change the scripts, then I need to save it and detach and re-attach the Debugger.

You should not need to detach and re-attach the debugger each time you make a change to a script. If the debugger is detaching itself, then you should try updating to the latest versions of Unity and Visual Studio. If you're manually detaching the debugger, just stop doing that.

Answer 2

This answer is for the original question; the asker completely rewrote the question into a new question.

Debug.Break() is useful if you need to look at what's going on in a scene at a specific point in time. Some example use cases:

• An character occasionally walks through a wall. When this happens, you want to pause the editor to check the character's speed, waypoints, and current animation.
• You have a coroutine which checks every 30 seconds for characters that are stuck and moves them until they're un-stuck. You want to see the before-and-after, so you set a Debug.Break() to pause the engine when 30 seconds have gone by and the coroutine is about to un-stick the characters.
• OnCollisionEnter() is occasionally getting called when you don't expect it, so you use Debug.Break() to pause the engine when a collision occurs so you can see what's causing the collision.

Any time that you need to pause the engine to examine the scene, but it's difficult or impossible to manually hit the pause button at exactly the right time, use Debug.Break().

Answer 3

If you look at Debug.log() in the official docs, it takes context as its second parameter, you can pass your Gameobject in that to know which object is calling the debug statement then call your Debug.break() to pause the scene.

Debug.log("myMessage",myGameObject);

Debug.break();