summaryrefslogtreecommitdiff
path: root/devel/kdbg
diff options
context:
space:
mode:
authorjmmv <jmmv@pkgsrc.org>2003-05-06 17:40:18 +0000
committerjmmv <jmmv@pkgsrc.org>2003-05-06 17:40:18 +0000
commitf1446ddf2bf8118f432b3ac74c88db3d832669a8 (patch)
tree37ae7d212f46ef8018a7bd8c13edba7da1a47ed9 /devel/kdbg
parent37170ce899bdf394cca1d0769b2215d84b15a7ee (diff)
downloadpkgsrc-f1446ddf2bf8118f432b3ac74c88db3d832669a8.tar.gz
Drop trailing whitespace. Ok'ed by wiz.
Diffstat (limited to 'devel/kdbg')
-rw-r--r--devel/kdbg/DESCR16
1 files changed, 8 insertions, 8 deletions
diff --git a/devel/kdbg/DESCR b/devel/kdbg/DESCR
index 8ae9086f2fd..a1262ba7e9c 100644
--- a/devel/kdbg/DESCR
+++ b/devel/kdbg/DESCR
@@ -1,24 +1,24 @@
KDbg is a graphical user interface to gdb, the GNU debugger. It provides an
intuitive interface for setting breakpoints, inspecting variables, and stepping
-through code.
+through code.
KDbg requires KDE, the K Desktop Environment, but you can of course debug any
-program.
+program.
Features:
-o Inspection of variable values in a tree structure.
+o Inspection of variable values in a tree structure.
o Direct member: For certain compound data types the most important
member values are displayed next to the variable name, so that it is
not necessary to expand the subtree of that variable in order to see
the member value. For example, you don't need to go into a variable of
type QString if you want to see the string that the variable holds.
KDbg can also display Qt 2.0's QString values, which are Unicode
- strings.
+ strings.
o Debugger at your finger tips: The basic debugger functions (step, next,
run, finish, until, set/clear/enable/disable breakpoint) are bound to
- function keys F5 through F10. Quick and easy.
+ function keys F5 through F10. Quick and easy.
o Of course, lots of other basic functions: View source code, search
text, set program arguments and environment variables, display
- arbitrary expressions. Everything you need to debug a program, eh!
-o Debugging of core dumps, attaching to running processes is possible.
-o Conditional breakpoints.
+ arbitrary expressions. Everything you need to debug a program, eh!
+o Debugging of core dumps, attaching to running processes is possible.
+o Conditional breakpoints.