[Lldb-commits] [PATCH] Refactor GdbRemote test cases to support remote platforms

[Tamas Berghammer]

As far as I know spawnSubprocess() generally used in test cases where lldb (LLGS) attach to an already running process, where the Install is necessary.

In this patch I address issues related to test cases testing the gdb protocol of LLGS with launching it on the target and then connecting to it with a socket. I use the spawnSubprocess() to start LLGS (in gdbserver mode) before connecting to it from python.

The option to disable the installation of the specified executable by spawSubprocess is required, because I have to start the same process as lldb-platform (actually lldb-server) and it can be too big to transfer it over to the remote target (~35 MB release, ~850 MB debug).


http://reviews.llvm.org/D8202

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/