# HG changeset patch # User timkelly # Date 1287073644 18000 # Node ID ac14826aa14b0104e1b930c6d9a668cb37fc23cc # Parent 90c82caa691853793c3e4482c99e4747fddbc170# Parent 76029713f5704fbf7d9a7d2637ab8943c65ac254 merge commit diff -r 90c82caa6918 -r ac14826aa14b core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Thu Oct 14 11:26:55 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Thu Oct 14 11:27:24 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