DAP "evaluate" request issued for invalid frameId #95367
Description
Created from microsoft/debug-adapter-protocol#60 (comment)
In microsoft/debugpy#112, we're seeing VSCode send "evaluate" requests with invalid "frameId" - they're sequenced immediately after "continue" or "next", which invalidates frame IDs for all frames retrieved prior to unpausing.
This came via a user-reported bug, for which we do not have our own repro. However, the user can repro it consistently and collect the logs.
The bug itself is about VSCode remote (SSH) sessions crashing during debugging, and in all cases, it appears that the crash immediately follows the IDE receiving a failure response to such an "evaluate" request. When DAP logging is enabled on both sides of the session, the client logs end when the request is sent, but the debug adapter logs show the request was received, processed, failed (due to invalid "frameId"), and failure response was sent back, after which the client disconnects eventually. We are not entirely sure that this problem is the root cause of the crashes, but given that this sequence of requests and responses shows up in all repro attempts so far, it's hard to believe that it is unrelated.
