summaryrefslogtreecommitdiff
path: root/devel/gdb/pkg/DESCR
diff options
context:
space:
mode:
authoragc <agc@pkgsrc.org>1999-07-01 15:26:19 +0000
committeragc <agc@pkgsrc.org>1999-07-01 15:26:19 +0000
commitddd3b276238b60298cdc9acd1d81ba13a49cb838 (patch)
tree0e42adbc6f0dec340bdfc56a8bcddc3f6b42e502 /devel/gdb/pkg/DESCR
parent6ec4a04ad49f5d3ce400fcebdc58f6bcfd4e4a6e (diff)
downloadpkgsrc-ddd3b276238b60298cdc9acd1d81ba13a49cb838.tar.gz
Initial import of gdb-4.18, the GNU symbolic debugger, into the NetBSD
packages collection. This package is only for Solaris - it is part of the base NetBSD system.
Diffstat (limited to 'devel/gdb/pkg/DESCR')
-rw-r--r--devel/gdb/pkg/DESCR18
1 files changed, 18 insertions, 0 deletions
diff --git a/devel/gdb/pkg/DESCR b/devel/gdb/pkg/DESCR
new file mode 100644
index 00000000000..1f94ea859cc
--- /dev/null
+++ b/devel/gdb/pkg/DESCR
@@ -0,0 +1,18 @@
+ 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.
+
+ * 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.
+
+