OS: Ubuntu 22.04.1 LTS (Debugged over an SSH session from Win 10 Pro).
VSCode version: 1.77.3
CodeLLDB version: 1.9.1
Compiler: 1.69.0
Debuggee: x86_64-unknown-linux-gnu
Issue:
Breakpoints get hit on time, but their handling by the IDE comes at a great delay (2-3 mins+).
How it was reproduced:
I have an external heartbeat process that monitors the health status of the debuggee, I also have a BP set in the latter.
After running many tests, it seems that 2-3 mins+ after the second process stops receiving heartbeats, is when the IDE handles the breakpoint and reflects the proper debugging UI to delegate control to me => The breakpoint seems to be hit on time, but the IDE fails to acknowledge it immediately, rather minutes later.
Based on the lastest issues I've checked like #907, some may assume that the whole extension is not working altogether, while in reality, they might be having a similar issue.
vadimcn
commented
1 year ago
OS: Ubuntu 22.04.1 LTS (Debugged over an SSH session from Win 10 Pro). VSCode version: 1.77.3 CodeLLDB version: 1.9.1 Compiler: 1.69.0 Debuggee: x86_64-unknown-linux-gnu
Issue:
Breakpoints get hit on time, but their handling by the IDE comes at a great delay (2-3 mins+).
How it was reproduced:
I have an external heartbeat process that monitors the health status of the debuggee, I also have a BP set in the latter. After running many tests, it seems that 2-3 mins+ after the second process stops receiving heartbeats, is when the IDE handles the breakpoint and reflects the proper debugging UI to delegate control to me => The breakpoint seems to be hit on time, but the IDE fails to acknowledge it immediately, rather minutes later.
Based on the lastest issues I've checked like #907, some may assume that the whole extension is not working altogether, while in reality, they might be having a similar issue.