## Auto-Targeting of Executables

In run-mode the Carbide debugger now supports the auto-targeting of processes that are already running or are created during the execution of the debug session. Previously, the debugger forced users to explicitly attach to a running process. Now, the debugger attempts to target all the EXEs and binaries like DLLs specified in the Executables tab of the launch configuration.

- If the executables are already started, it gets the load address of the executable and targets it for debugging, resolving any breakpoints it finds.
- The debugger will target any executable not already started whenever a "process load" event occurs, resolving its breakpoints as well.

#### Debugging DLLs

One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view. See Attaching to a OS Process for more details.

##### Other References

- Executables
- Attaching to a Process