There's currently a lot of ways to launch processes, and the interactions that lead to specific methods being chosen can be a bit confusing sometimes.
Out of curiosity, if a plugin supports launching under a debugger directly, why is the separate start stopped / attach / resume algorithm used? It seems more straightforward. If someone gets themselves through that codepath, argdumper won't be used. Which is confusing if you're outside looking in at the API. From the outside you just see the process gets launched using a supported mechanism for launching processes, and it ignores the flag. http://reviews.llvm.org/D7743 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
