Open doraeric opened 11 months ago
I have a similar situation while debugging C++ code on a linux host, the last part of the log is quite similar,. Interestingly, sometimes it works. I was able to relate it to the usage of a 3rd party library, but the behaviour is still strange as sometimes it just works. Starting the app from lldb manually works fine, and also gdb has no issues handling the app.
LE: OS: pop 22.04, VSCode 1.85.2 codelldb: 1.10-dev (I installed the latest at some point hoping that it will fix it), compiler: gcc 11+
Here is the last part of my log:
[DEBUG codelldb::debug_session] Debug event: 0x77280c007690 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = stopped}
[DEBUG codelldb::debug_session] Debug event: 0x7727a845ade0 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = running}
[DEBUG codelldb::dap_codec] <-- {"seq":71,"type":"event","event":"continued","body":{"allThreadsContinued":true,"threadId":65419}}
[DEBUG codelldb::debug_session] Debug event: 0x77280c0077a0 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = stopped}
[DEBUG codelldb::debug_session] Debug event: 0x7727a847f9f0 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = running}
[DEBUG codelldb::dap_codec] <-- {"seq":72,"type":"event","event":"continued","body":{"allThreadsContinued":true,"threadId":65419}}
[DEBUG codelldb::debug_session] Debug event: 0x77280c000cd0 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = stopped}
[DEBUG codelldb::debug_session] Debug event: 0x7727a845a090 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = running}
[DEBUG codelldb::dap_codec] <-- {"seq":73,"type":"event","event":"continued","body":{"allThreadsContinued":true,"threadId":65419}}
[DEBUG codelldb::debug_session] Debug event: 0x77280c007880 Event: broadcaster = 0x5da2ce3a51d8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x5da2ce3a51a0 (pid = 65419), state = exited}
[DEBUG codelldb::dap_codec] <-- {"seq":74,"type":"event","event":"output","body":{"category":"console","output":"Process exited with code -1.\n"}}
[DEBUG codelldb::dap_codec] <-- {"seq":75,"type":"event","event":"exited","body":{"exitCode":-1}}
[DEBUG codelldb::dap_codec] <-- {"seq":76,"type":"event","event":"terminated","body":{}}
[DEBUG codelldb::dap_codec] --> {"command":"disconnect","arguments":{"restart":false,"terminateDebuggee":false},"type":"request","seq":12}
[DEBUG codelldb::dap_codec] <-- {"seq":77,"type":"response","request_seq":12,"success":true,"command":"disconnect"}
[DEBUG codelldb::dap_session] Client has disconnected
[DEBUG codelldb::debug_session] End of the requests stream
[DEBUG codelldb::debug_session] DebugSession::drop()
[DEBUG codelldb] End of the debug session
[DEBUG codelldb] Exiting
OS: Debian GNU/Linux 12 (bookworm) VSCode version: 1.85.1 CodeLLDB version: v1.10.0 Compiler: rustc 1.75.0 (82e1608df 2023-12-21) Debuggee:
The log is from a docker container on windows, but I can reproduce this issue on a linux host. I am debugging rust program in vs code. When I set breakpoints before using
rayon
par_iter
, I can see the output in vs code terminal. Then I go forward to next line one by one, and the program just stops. There is no any further error message nor program output in vs code terminal.Here is the code to reproduce the issue:
With
cargo run
, I can see "after parallel cmds" and outputs, but I can't see these messages when debugging. If the code runs normally when debugging, increase the number of cmds, and it should be reproduced.Verbose log