suggestion - remove __debugbreak()

During debug sessions I have to hit g for go repeatedly, once for each LogError() until eventually I reach the access violation or whatever exception I really care about. Too many {g, Enter} keyboard strikes can cause the desired exception to be missed, since the repetition becomes mindless at times.
Alternatively, ifdef that code section.

if (IsDebuggerPresent())
    {
        try
        {
            __debugbreak();
        }
        // SEH Exceptions are sent through C++ handlers in the instrumentation engine.
        catch (...)
        {
        }
    }

Start by searching the repository for __debugbreak() and the surrounding LogError() handling shown in the issue. Read how debugger detection and SEH exceptions are handled there, then check existing tests or debug-build instructions if available. Done means the repeated debugger breaks are removed or made optional without hiding the access violation or other exception the developer is investigating.