Our users see a lot of activity in terms of error pop-ups.

• Race conditions between long lasting (and/or by the IDE delayed) window updates and user interaction like stepping/resume. (Late request arrivals from views, requests already fed into GDB command queue which then fail on GDB level after target state change).
• Views in other VS Code extensions not immediately ceasing to send DAP requests while the debug adapter is already shutting down.
• Recently introduced command queue flushing for graceful shutdown throws unhandled errors.

These things make the solution look premature and buggy. And users normally can't do anything about such situations. And most of the times they wouldn't even miss the lack of accurately returned data or errors in such corner cases. Accurate view updates become irrelevant during shutdown. And when setting the CPU running/stepping either views go blank anyway (non-aux-gdb mode), or get updated during the next periodic refresh/stopped event which is normally acceptable for users (note that this could be further refined in future by returning cached data, e.g. for variables, but I don't see an urgent need for that right now, hence returning responses with empty data should be fine).