summaryrefslogtreecommitdiff
path: root/devel
diff options
context:
space:
mode:
authorwiz <wiz@pkgsrc.org>1999-12-28 05:21:19 +0000
committerwiz <wiz@pkgsrc.org>1999-12-28 05:21:19 +0000
commit67f381f6998f3da205d7ebec217d2f638974f13e (patch)
tree2ad31f4d22a3aacf450a9e5b0f1c0760d29b6726 /devel
parenteaff922bb000f91dbbf8fa1bc8cf378695af6845 (diff)
downloadpkgsrc-67f381f6998f3da205d7ebec217d2f638974f13e.tar.gz
reformatted description, removing unnecessary whitespace
Diffstat (limited to 'devel')
-rw-r--r--devel/gdb/pkg/DESCR23
1 files changed, 11 insertions, 12 deletions
diff --git a/devel/gdb/pkg/DESCR b/devel/gdb/pkg/DESCR
index 1f94ea859cc..c7c22076938 100644
--- a/devel/gdb/pkg/DESCR
+++ b/devel/gdb/pkg/DESCR
@@ -1,18 +1,17 @@
- The purpose of a debugger such as GDB is to allow you to see what is
-going on "inside" another program while it executes--or what another
-program was doing at the moment it crashed.
-
- GDB can do four main kinds of things (plus other things in support of
-these) to help you catch bugs in the act:
+ The purpose of a debugger such as GDB is to allow you to see what
+is going on "inside" another program while it executes--or what
+another program was doing at the moment it crashed.
+
+ GDB can do four main kinds of things (plus other things in support
+of these) to help you catch bugs in the act:
* Start your program, specifying anything that might affect its
behavior.
-
- * Make your program stop on specified conditions.
+
+ * Make your program stop on specified conditions.
* Examine what has happened, when your program has stopped.
-
- * Change things in your program, so you can experiment with
- correcting the effects of one bug and go on to learn about another.
-
+ * Change things in your program, so you can experiment with
+ correcting the effects of one bug and go on to learn about
+ another.