diff --git a/docs/HowTo/HowToCaptureLog.aml b/docs/HowTo/HowToCaptureLog.aml index 4e47d1b7d..fd04776d6 100644 --- a/docs/HowTo/HowToCaptureLog.aml +++ b/docs/HowTo/HowToCaptureLog.aml @@ -36,28 +36,28 @@ -
- Attaching to a Process +
+ Injecting into a Process - It is possible to attach to an already running process. By selecting the "Attach to Process" + It is possible to inject to an already running process. By selecting the "Inject to Process" entry in the File menu, the capture dialog will modify to list the running processes rather than asking for an executable and command line parameters. This can be useful if launching your application from a single exe is non-trivial and it's - easier to attach to the process after it has been launched. + easier to inject into the process after it has been launched. -Attaching to a selected existing process. - +Injecting to a selected existing process. + - The important thing to note about attaching is that RenderDoc can only attach to processes that + The important thing to note about injecting is that RenderDoc can only inject to processes that have not initialised or used the target API. If this is the case RenderDoc can insert its hooks before any use of the API and work as normal. If the API has been used or initialised the results are undefined and likely RenderDoc will simply not function as it's too late to hook in. - If RenderDoc is not running as administrator, it cannot attach to processes that are running with + If RenderDoc is not running as administrator, it cannot inject into processes that are running with elevated permissions. In this case you can either run RenderDoc as administrator (not recommended unless necessary), or re-run the process as the normal user running RenderDoc. diff --git a/docs/Windows/CaptureDialog.aml b/docs/Windows/CaptureDialog.aml index 37cb6969d..5427def8d 100644 --- a/docs/Windows/CaptureDialog.aml +++ b/docs/Windows/CaptureDialog.aml @@ -3,7 +3,7 @@ - The Capture Dialog (which doubles as the attach-to-process dialog) is the + The Capture Dialog (which doubles as the inject-into-process dialog) is the single point where programs are launched and logfiles are captured to disk. After launching a capture a connection dialog will open to allow you to manage and open any captures you take. See for more details. @@ -44,23 +44,23 @@
-
+
Inject into Process When invoked through Inject into Process the capture dialog modifies itself to give a list of processes running on the target system. A list of processes is fetched once when the dialog is opened, but this can be refreshed - by clicking on the refresh button below the list. Select the process you would like to attach to - and click Attach. + by clicking on the refresh button below the list. Select the process you would like to inject into + and click Inject. -Attaching to an already-running process via RenderDoc. - +Injecting into an already-running process via RenderDoc. + The process must not have invoked or initialised the API to be used, as this will be too late for RenderDoc to hook and capture it. At best RenderDoc will not capture, at worst - it may cause crashes or undefined behaviour. Only attach to processes you can guarantee are early + it may cause crashes or undefined behaviour. Only inject to processes you can guarantee are early enough in their initialisation that they have not used the graphics API.