Looks good. Jean-Daniel:
When you get to the point where you start filling in the functions for anything that stores up info for when a process is to be launched (setting environment variables, setting working directory, setting launch architecture), we should have GDBRemoteCommunicationServer have ProcessLaunchInfo and ProcessAttachInfo member variables that can be slowly filled in. Then when the 'A' packet, or any of the vAttach packets come in, we can use the current ProcessLaunchInfo or ProcessAttachInfo member variable to do the launching/attaching. On Dec 5, 2013, at 12:43 AM, Jean-Daniel Dupas <[email protected]> wrote: > http://llvm-reviews.chandlerc.com/D2337 > > Files: > source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServer.cpp > source/Utility/StringExtractorGDBRemote.cpp > source/Utility/StringExtractorGDBRemote.h > <D2337.1.patch>_______________________________________________ > lldb-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
