# HG changeset patch # User fturovic # Date 1286996849 18000 # Node ID fb8db13ce8401b3c4089840408d279e9e2d4729f # Parent 5dd5b87d0ddf2c44c341bbed07d76f893127500c BUG 12329 - Reworded to add simulator target as well diff -r 5dd5b87d0ddf -r fb8db13ce840 core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Wed Oct 13 14:01:23 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Wed Oct 13 14:07:29 2010 -0500 @@ -15,7 +15,7 @@
  • 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 Process for more details.

    +

    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 don't know which process to attach to or 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 Process for more details.

    Other References