https://github.com/labath commented:
would `runCmd("platform select remote-linux")` have the same effect?
That would make the test more realistic, as that's how you would debug a
non-local process. The problem right now is that lldb selects the host platform
by default (you could argue that it shouldn't do that for "gdb-remote"
connections, but that's what it is right now), and unless that platform rejects
it (which happens when there's a host-binary architecture mismatch), it will
bind the target to that platform. remote-linux (or maybe `remote-gdb-server` ?)
is what would get selected then, so this will also make sure the behavior of
the test is consistent between aarch64 and non-aarch64 runs.
https://github.com/llvm/llvm-project/pull/157432
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
