Breakpoint triggered in Visual Studio after running "{,,UE4Editor-Core}::PrintScriptCallstack()" command

Running the command

 {,,UE4Editor-Core}::PrintScriptCallstack() 

in the Immediate Window in Visual Studio while debugging is paused in Visual Studio will result in a breakpoint being hit when the debug session is resumed.

REGRESSION:
Yes. This breakpoint was not triggered in 4.17.2.

1. Create a new Basic Code project.
2. Start a new debug instance of the project in Visual Studio.
3. Once the project opens in the Editor, click the Break All (pause) button in Visual Studio.
4. Open the Immediate Window in Visual Studio (Ctrl+Alt+I or Debug -> Windows -> Immediate).
5. In the Immediate Window, enter the following command:

    {,,UE4Editor-Core}::PrintScriptCallstack() 

6. Click the Continue (play) button in Visual Studio.

RESULT:
A breakpoint is triggered with the following error: Exception thrown at 0x0000000000000000 in UE4Editor.exe: 0xC0000005: Access violation executing location 0x0000000000000000.

EXPECTED:
The debug session resumes.