Files
cmake/Source
Christopher Wellons 3490eff6f5 debugger: fix infinite loop when debugger pipe is closed
When a DAP client closes the pipe (or crashes), getPayload() returns an
empty functor without triggering the onError handler, so SessionActive
is never set to false and the session thread spins in a tight loop at
100% CPU. Handle the empty-payload case with the same cleanup performed
by the onError and DisconnectRequest handlers.

testProtocolWithPipesAbruptDisconnect drives the DAP handshake and then
closes the client side of the pipe without sending a DisconnectRequest.
The test deliberately avoids ReportExitCode so that no concurrent write
triggers the dap::Session error handler and masks the busy-loop
condition; if the SessionThread spins on EOF, the adapter destructor
blocks in SessionThread.join() and the test fails on a 10-second
timeout.

Fixes: #27743
2026-04-09 10:56:14 -04:00
..
2026-03-20 08:56:19 -04:00
2026-04-09 00:04:53 -04:00
2026-03-12 14:00:59 -04:00
2026-01-29 10:16:59 -05:00
2026-03-10 11:46:49 -04:00
2025-08-01 09:56:00 -04:00
2025-11-12 14:54:35 -05:00
2025-10-07 09:29:18 -04:00
2025-08-26 14:29:01 -07:00
2026-01-13 11:29:23 -05:00
2026-04-02 13:23:54 -04:00
2026-01-27 18:15:26 +01:00
2025-11-12 14:54:35 -05:00
2025-11-12 14:54:35 -05:00
2026-02-03 09:34:23 +03:00
…