summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2018-08-30 19:14:02 +0000
committerPavel Labath <pavel@labath.sk>2018-08-30 19:14:02 +0000
commita95c33f6006bcccf38236c9e960d013e4fc1947c (patch)
treed125e7bd13dbb275dfc259fa08ce69387d95e6d6 /lldb/packages/Python/lldbsuite/test/functionalities
parent2123ea7d5c722e98ce0f047c8baa3fb3db23e6b3 (diff)
downloadbcm5719-llvm-a95c33f6006bcccf38236c9e960d013e4fc1947c.tar.gz
bcm5719-llvm-a95c33f6006bcccf38236c9e960d013e4fc1947c.zip
Fix deadlock in gdb-client tests
Using a listen queue of length 0 caused a deadlock on my machine in the gdb-client tests while attempting to establish the loopback socket connection. I am not sure if this is down to a different python or kernel version, but in either case, having queue of length zero sounds like a bad idea, so I'm bumping that to one (which also fixes the deadlock). llvm-svn: 341096
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities')
-rw-r--r--lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py b/lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py
index d8d759a5dd5..b86a0c6bad8 100644
--- a/lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py
+++ b/lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py
@@ -246,7 +246,7 @@ class MockGDBServer:
addr = ("127.0.0.1", self.port)
self._socket.bind(addr)
self.port = self._socket.getsockname()[1]
- self._socket.listen(0)
+ self._socket.listen(1)
self._thread = threading.Thread(target=self._run)
self._thread.start()
OpenPOWER on IntegriCloud