Post

Replies

Boosts

Views

Activity

Reply to LLDB always exits abnormally on local code
No solution, sorry, but I have exactly the same problem. I can debug successfully a local program on Sonoma 14.2.1 on an M2, but when trying to debug the same code/program on Sonoma 14.2.1 on a 2019 Intel i5, I repeatedly get the "lost connection" outcome after setting a breakpoint at main(): (lldb) target create "factorial" Current executable set to '/Users/chris/src/showc/showc/src/factorial' (x86_64). (lldb) br set -n main Breakpoint 1: where = factorial`main + 22 at factorial.c:30:9, address = 0x0000000100000e96 (lldb) run Process 85314 launched: '/Users/chris/src/showc/showc/src/factorial' (x86_64) Process 85314 exited with status = -1 (0xffffffff) lost connection The frequent suggestion of using settings set plugin.process.gdb-remote.packet-timeout 300 has no effect.
Jan ’24