[Lldb-commits] [PATCH] convert gdb-remote 'A' launch to use LaunchProcess ()

Todd Fiala tfiala at google.com
Mon Jan 27 09:50:29 PST 2014

Proposed change:

convert gdb-remote 'A' launch to use LaunchProcess ()

This change modifies the 'A' command handler's launch code to launch with
LaunchProcess ().  The net effect is that the default process monitoring
that LaunchProcess () adds will kick in, allowing the
GDBRemoteCommunicationServer to be able to reap processes started with this
facility correctly.  Later, in the case of lldb-gdbserver, we'll also have
the proper process monitoring going on to really debug the inferior process.

Any issues with this?  This code runs both in lldb-gdbserver and

--- source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServer.cpp
+++ source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServer.cpp (working
@@ -811,8 +811,11 @@

     if (success)
+        // FIXME: remove linux restriction once eLaunchFlagDebug is
+#if !defined (__linux__)
         m_process_launch_info.GetFlags().Set (eLaunchFlagDebug);
-        m_process_launch_error = Host::LaunchProcess
+        m_process_launch_error = LaunchProcess ();
         if (m_process_launch_info.GetProcessID() !=
             return SendOKResponse ();

Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20140127/397dc023/attachment.html>

More information about the lldb-commits mailing list