| Issue |
158165
|
| Summary |
[lldb] Debugging fails to launch on 32-bit systems (i686, armv7l) with "Lost debug server connection"
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
patryk4815
|
I tested lldb on i686 (x86-32) and armv7l on both systems lldb fails to start debugging:
```console
root@(none):/# lldb ./hello.arm
(lldb) target create "./hello.arm"
Current executable set to '/hello.arm' (arm).
(lldb) log enable gdb-remote all
(lldb) b main
Breakpoint 1: where = hello.arm`main + 20 at hello.c:4:5, address = 0x00023a4c
(lldb) r
lldb ProcessGDBRemote::DoLaunch() entered
lldb ProcessGDBRemote::DoLaunch no STDIO paths given via launch_info
lldb failed to connect to debugserver: Lost debug server connection
error: Lost debug server connection
(lldb) version
lldb version 20.1.2
root@(none):/# uname -a
Linux (none) 6.16.3 #1 SMP Mon Sep 8 17:53:59 UTC 2025 armv7l armv7l armv7l GNU/Linux
```
For example on any other 64bit architecture lldb works fine and log output is different:
```console
~ # /tmp/pwndbg/bin/lldb /mnt/hello.s390x
(lldb) target create "/mnt/hello.s390x"
Current executable set to '/mnt/hello.s390x' (s390x).
(lldb) b main
Breakpoint 1: where = hello.s390x`main + 20 at hello.c:4:5, address = 0x00000000010092e4
(lldb) log enable gdb-remote all
(lldb) r
lldb ProcessGDBRemote::DoLaunch() entered
lldb ProcessGDBRemote::DoLaunch provided with STDIO paths via launch_info: stdin=/dev/pts/0, stdout=/dev/pts/0, stderr=/dev/pts/0
lldb GDBRemoteCommunication::StartDebugserverProcess(url="" port=0)
lldb GDBRemoteCommunication::GetDebugserverPath() gdb-remote stub exe path set from environment variable: /tmp/pwndbg/bin/lldb-server
lldb launch info for gdb-remote stub:
..... <TRUNCATED>
```
I think main issue is something not right with `"no STDIO paths given via launch_info"`. No idea if this is issue with my qemu-system setup.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
