diff options
| author | wiz <wiz> | 1999-12-28 05:21:19 +0000 |
|---|---|---|
| committer | wiz <wiz> | 1999-12-28 05:21:19 +0000 |
| commit | 1a875a1aea578bf30f4cad1212dc0fed0f7254ce (patch) | |
| tree | 2ad31f4d22a3aacf450a9e5b0f1c0760d29b6726 | |
| parent | c50ff704551fb308976118720709746ca2d65531 (diff) | |
| download | pkgsrc-1a875a1aea578bf30f4cad1212dc0fed0f7254ce.tar.gz | |
reformatted description, removing unnecessary whitespace
| -rw-r--r-- | devel/gdb/pkg/DESCR | 23 |
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. |