gcc484ntopperl-5.22
|
Last change
on this file since 0105685 was
c5c522c,
checked in by Edwin Eefting <edwin@datux.nl>, 8 years ago
|
|
initial commit, transferred from cleaned syn3 svn tree
|
-
Property mode set to
100644
|
|
File size:
1.2 KB
|
| Rev | Line | |
|---|
| [c5c522c] | 1 | # HOW TO EDIT THIS FILE: |
|---|
| 2 | # The "handy ruler" below makes it easier to edit a package description. Line |
|---|
| 3 | # up the first '|' above the ':' following the base package name, and the '|' |
|---|
| 4 | # on the right side marks the last column you can put a character in. You must |
|---|
| 5 | # make exactly 11 lines for the formatting to be correct. It's also |
|---|
| 6 | # customary to leave one space after the ':'. |
|---|
| 7 | |
|---|
| 8 | |-----handy-ruler------------------------------------------------------| |
|---|
| 9 | gdb: gdb (the GNU symbolic debugger) |
|---|
| 10 | gdb: GDB, the GNU Project debugger, allows you to see what is going on |
|---|
| 11 | gdb: inside another program while it executes -- or what another program |
|---|
| 12 | gdb: was doing at the moment it crashed. GDB can do four main kinds of |
|---|
| 13 | gdb: things to help you catch bugs in the act: 1) Start your program, |
|---|
| 14 | gdb: specifying anything that might affect its behavior. 2) Make your |
|---|
| 15 | gdb: program stop on specified conditions. 3) Examine what has happened, |
|---|
| 16 | gdb: when your program has stopped. 4) Change things in your program, so |
|---|
| 17 | gdb: you can experiment with correcting the effects of one bug and go on |
|---|
| 18 | gdb: to learn about another. The program being debugged can be written in |
|---|
| 19 | gdb: Ada, C, C++, Objective-C, Pascal and many other languages. |
|---|
Note: See
TracBrowser
for help on using the repository browser.
