From be82b6698429fb73fcf3611000689c7b4a25f6a6 Mon Sep 17 00:00:00 2001 From: Johannes Sixt Date: Sun, 29 Oct 2017 18:15:09 +0100 Subject: [PATCH] Update the English manual. - Adjust recently updated menu and window texts. - Remove outdated texts about threads. - Mention new memory dump feature. --- kdbg/doc/en/index.html | 18 ++++++------ kdbg/doc/en/invocation.html | 68 ++++++++++++++++++++++----------------------- kdbg/doc/en/memory.html | 4 ++- kdbg/doc/en/sourcecode.html | 4 +-- kdbg/doc/en/threads.html | 7 +---- kdbg/doc/en/tips.html | 9 ------ 6 files changed, 48 insertions(+), 62 deletions(-) rewrite kdbg/doc/en/invocation.html (67%) diff --git a/kdbg/doc/en/index.html b/kdbg/doc/en/index.html index 3eab831..1551927 100644 --- a/kdbg/doc/en/index.html +++ b/kdbg/doc/en/index.html @@ -58,7 +58,7 @@ though it offers a threads window).

with Settings|Global Options.

Specifying a debugging target

-

To debug a program, choose File|Executable from the menu. If you +

To debug a program, choose File|Load Executable from the menu. If you have debugged the program earlier, you can choose it from File|Recent Executables. The program is loaded.

If you want to debug a core dump, you must first load the executable @@ -167,18 +167,18 @@ arrange them in any manner you like.

Author

KDbg is written by Johannes Sixt -with contributions from these people (in no particular order):

+with contributions from many people, among others (in no particular order):

KDbg homepage is at http://www.kdbg.org/.

diff --git a/kdbg/doc/en/invocation.html b/kdbg/doc/en/invocation.html dissimilarity index 67% index bee14a9..3768f8c 100644 --- a/kdbg/doc/en/invocation.html +++ b/kdbg/doc/en/invocation.html @@ -1,35 +1,33 @@ - - - - - - KDbg - Invocation - - -

Contents

-

Invoking KDbg from the command line

-

-Usage: kdbg [Qt-options] [KDE-options] [options] [program] [core] 
-
-Generic options:
-  --help                    Show help about options
-  --help-qt                 Show Qt specific options
-  --help-kde                Show KDE specific options
-  --help-all                Show all options
-  --author                  Show author information
-  -v, --version             Show version information
-  --license                 Show license information
-  --                        End of options
-
-Options:
-  -t <file>                 transcript of conversation with the debugger
-  -r <device>               remote debugging via <device>
-  -l <language>             specify language: C, XSLT []
-  -a <args>                 specify arguments of debugged executable
-  -p <pid>                  specify PID of process to debug
-
-Arguments:
-  program                   path of executable to debug
-  core                      a core file to use
-

- + + + + + + KDbg - Invocation + + +

Contents

+

Invoking KDbg from the command line

+

+Usage: kdbg [options] [program] [core]
+A Debugger
+
+Options:
+  -h, --help                 Displays this help.
+  -v, --version              Displays version information.
+  --author                   Show author information.
+  --license                  Show license information.
+  --desktopfile <file name>  The base file name of the desktop entry for this
+                             application.
+  -t <file>                  transcript of conversation with the debugger
+  -r <device>                remote debugging via <device>
+  -l <language>              specify language: C, XSLT
+  -x                         use language XSLT (deprecated)
+  -a <args>                  specify arguments of debugged executable
+  -p <pid>                   specify PID of process to debug
+
+Arguments:
+  [program]                  path of executable to debug
+  [core]                     a core file to use
+

+ diff --git a/kdbg/doc/en/memory.html b/kdbg/doc/en/memory.html index d8dbab7..00faa82 100644 --- a/kdbg/doc/en/memory.html +++ b/kdbg/doc/en/memory.html @@ -10,7 +10,9 @@

The Memory Dump Window

The memory dump window is displayed using View|Memory. It displays -the contents of the program's memory at arbitrary adresses.

+the contents of the program's memory at arbitrary adresses. +When you scroll to the end of the area indicated by the scrollbar, additional +data is retrieved from memory automatically.

To display memory contents, enter an address in the edit field. The address need not be given in hexadecimal form - it can be an expression.

You can specifiy a format how the memory contents shall be displayed diff --git a/kdbg/doc/en/sourcecode.html b/kdbg/doc/en/sourcecode.html index de46381..9eb8f77 100644 --- a/kdbg/doc/en/sourcecode.html +++ b/kdbg/doc/en/sourcecode.html @@ -22,7 +22,7 @@ be clicked on. If you do so, the source line's assembler code will be displayed. The plus turns into a minus '-', which, if clicked, will hide the disassembled code.

Mostly, source code windows are opened automatically. To open a new -source file manually, click the right mouse button and choose Open Source -or choose File|Open Source.

+source file manually, click the right mouse button and choose Open Source Code +or choose File|Open Source Code.

diff --git a/kdbg/doc/en/threads.html b/kdbg/doc/en/threads.html index fd1470a..1c4a8c1 100644 --- a/kdbg/doc/en/threads.html +++ b/kdbg/doc/en/threads.html @@ -11,11 +11,6 @@ The Threads Window

The threads window is displayed using View|Threads. The threads window lists the active threads of the program.

-

Note: Debugging threaded programs must be supported by -the version of gdb that is used - it is not a feature of KDbg. For Linux -systems this works best with gdb5 and later. However, at the time of this writing gdb -still poorly supports threads on NPTL- (New Posix Threads Library) enabled -systems (glibc 2.3.x and kernel 2.6.x).

The contents of the threads window are updated every time the program is stopped by the debugger. (That is, the window does not reflect the state while the program is running.)

@@ -32,7 +27,7 @@ The local variables window displays the active thread's local variables.
  • -The watch window uses the active thread's local +The watched expressions window uses the active thread's local variables to evaluate the expressions.

    • By clicking a listed thread, the active thread is switched, and the corresponding diff --git a/kdbg/doc/en/tips.html b/kdbg/doc/en/tips.html index 4c360a3..86f1ae5 100644 --- a/kdbg/doc/en/tips.html +++ b/kdbg/doc/en/tips.html @@ -32,15 +32,6 @@ In order to make them effective, the program must stop at a time when the shared library is loaded. For this it is usually sufficient to set a breakpoint in main(). At the time when this breakpoint is hit, the orphaned breakpoints in the shared library become effective. - -

  • -Debugging multi-threaded programs on NPTL-enabled Linux systems (kernel 2.6.x -or later and glibc 2.3.x or later) may sometimes fails; gdb stops the program -at unexpected instances. In this case the following may help (using bash): -
    -LD_ASSUME_KERNEL=2.4.19 kdbg myprogram
-
    I.e. you run KDbg from the command line such that the old -Linuxthreads implementation is used.
    • -- 2.11.4.GIT