😂

I use this a lot in combination with a non-suspending breakpoint. There are situations where I know starting from here, it becomes interesting. Typically a state change or a specific point in an integration tests. Things not necessarily available on the call stack to write a condition for.

The debugger with its "Disable until hitting the following breakpoint" option is huge. Sometimes I'm thrown in front of a big legacy code base. This option is one of the things that enables me to tell what is actually going on, even in the most mind-boggling situations.