diff options
| author | zuntum <zuntum> | 2001-11-01 00:57:41 +0000 |
|---|---|---|
| committer | zuntum <zuntum> | 2001-11-01 00:57:41 +0000 |
| commit | 0b6b506536c1ff50f1531d26be2fccfe86c74335 (patch) | |
| tree | 93b6296152ccfbaa88b43de043b2d69ce6e63fc5 /devel/gdb/DESCR | |
| parent | 1b9f41a39161bad144fdeb94a0e51fa8ba7c309a (diff) | |
| download | pkgsrc-0b6b506536c1ff50f1531d26be2fccfe86c74335.tar.gz | |
Move pkg/ files into package's toplevel directory
Diffstat (limited to 'devel/gdb/DESCR')
| -rw-r--r-- | devel/gdb/DESCR | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/devel/gdb/DESCR b/devel/gdb/DESCR new file mode 100644 index 00000000000..c7c22076938 --- /dev/null +++ b/devel/gdb/DESCR @@ -0,0 +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: + + * 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. |