[all-commits] [llvm/llvm-project] c3193e: [lldb/ipv6] Support running lldb tests in an ipv6-...

[Jordan Rupprecht via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: c3193e464cbd5e8b7cade103032c222bf8bc0e27
      https://github.com/llvm/llvm-project/commit/c3193e464cbd5e8b7cade103032c222bf8bc0e27
  Author: Jordan Rupprecht <rupprecht at google.com>
  Date:   2020-09-30 (Wed, 30 Sep 2020)

  Changed paths:
    M lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
    M lldb/test/API/functionalities/gdb_remote_client/gdbclientutils.py
    M lldb/test/API/tools/lldb-server/commandline/TestStubReverseConnect.py
    M lldb/tools/lldb-server/lldb-gdbserver.cpp
    M lldb/unittests/Host/SocketTest.cpp
    M lldb/unittests/Host/SocketTestUtilities.cpp

  Log Message:
  -----------
  [lldb/ipv6] Support running lldb tests in an ipv6-only environment.

When running in an ipv6-only environment where `AF_INET` sockets are not available, many lldb tests (mostly gdb remote tests) fail because things like `127.0.0.1` don't work there.

Use `localhost` instead of `127.0.0.1` whenever possible, or include a fallback of creating `AF_INET6` sockets when `AF_INET` fails.

Reviewed By: labath

Differential Revision: https://reviews.llvm.org/D87333