diff options
Diffstat (limited to 'doc/kdevelop/debugger.docbook')
| -rw-r--r-- | doc/kdevelop/debugger.docbook | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/kdevelop/debugger.docbook b/doc/kdevelop/debugger.docbook index a06f2c83..247d26ff 100644 --- a/doc/kdevelop/debugger.docbook +++ b/doc/kdevelop/debugger.docbook @@ -3,7 +3,7 @@ <indexterm zone="debugger"><primary>debugger</primary></indexterm> <para> -For C and C++, &kdevelop; contains an internal debugger that is directly +For C and C++, &tdevelop; contains an internal debugger that is directly integrated with the editor. Technically, it is implemented as a frontend that uses the portable &GNU; debugger <application>gdb</application> through a pipe. The debugger can be started in several ways: @@ -100,13 +100,13 @@ via the context menu. <indexterm zone="debugger"><primary>breakpoints</primary></indexterm> <para> This window allows you to see and manipulate the breakpoints. Remember that -&kdevelop; uses <application>GDB</application>, so to fully understand the -&kdevelop; debugging features, you should know a little bit about the <ulink +&tdevelop; uses <application>GDB</application>, so to fully understand the +&tdevelop; debugging features, you should know a little bit about the <ulink url="http://www.gnu.org/software/gdb">GDB</ulink>. </para> <para>If you want to look at the source code, breakpoints are defined in -<filename>kdevelop/languages/cpp/debugger/breakpoint.h</filename>. +<filename>tdevelop/languages/cpp/debugger/breakpoint.h</filename>. </para> <para>At the left edge, the window has buttons to:</para> @@ -215,10 +215,10 @@ The debugger backend <application>gdb</application> does not allow to set breakpoints within code that is not currently loaded. In a highly modular application, where often code is only loaded on demand as a plugin (using the libc function <function>dlopen(3)</function>), this can be inconvenient. -Therefore, &kdevelop; rolls its own support for breakpoints in shared +Therefore, &tdevelop; rolls its own support for breakpoints in shared libraries. If you set this option, it allows you to set breakpoints in libraries which are not loaded. Then, whenever <application>gdb</application> -notifies that a library is loaded, &kdevelop; tries to set the pending +notifies that a library is loaded, &tdevelop; tries to set the pending breakpoints. </para> </listitem> |