Stopping due to fatal error: ProtocolException: Cannot evaluate expression on the specified stack frame.

Environment

VS Code version: Code 1.67.1 (https://github.com/microsoft/vscode/commit/da15b6fd3ef856477bf6f4fb29ba1b7af717770d, 2022-05-06T12:39:22.915Z)
OS version: Linux x64 5.17.5-76051705-generic
Restricted Mode: No

System Info
Item Value
CPUs AMD Ryzen 9 5900HS with Radeon Graphics (4 x 3293)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) 1, 1, 1
Memory (System) 15.59GB (1.04GB free)
Process Argv --unity-launch --crash-reporter-id 5fbb5169-0367-4f2f-bcc4-b836ec4f5014
Screen Reader no
VM 100%
DESKTOP_SESSION pop
XDG_CURRENT_DESKTOP Unity
XDG_SESSION_DESKTOP pop
XDG_SESSION_TYPE x11
Connection to 'SSH: mainframe' could not be established Canceled

Extensions (11)
Extension Author (truncated) Version
vscode-fix-checksums leh 1.1.0
python ms- 2022.6.2
vscode-pylance ms- 2022.5.1
jupyter ms- 2022.4.1021342353
jupyter-keymap ms- 1.0.0
jupyter-renderers ms- 1.0.6
remote-ssh ms- 0.80.0
remote-ssh-edit ms- 0.80.0
cpptools ms- 1.9.8
makefile-tools ms- 0.5.0
material-theme zhu 3.13.29
(2 theme extensions excluded)

Bug Summary and Steps to Reproduce

Bug Summary:

Steps to reproduce:

1. In this environment...
2. With this config...
3. Do '...'
4. See error...

Debugger Configurations

NA

Debugger Logs

NA

Other Extensions

No response

Additional Information

Issue Type: Bug

Debug any C++ code remote or local.

Stepping through eventually results in "Stopping due to fatal error: ProtocolException: Cannot evaluate expression on the specified stack frame."

This did not happen with the previous version(s) of vscode.

No source files, tests, or debugger configuration are named. Begin by reproducing the C++ stepping failure in the supplied Linux and VS Code 1.67.1 environment, then compare it with the previous version to isolate the trigger; done means the fatal ProtocolException no longer occurs for the confirmed case.