summaryrefslogtreecommitdiffstats
path: root/slackware64-current/slackware64/d/gdb-7.10.1-x86_64-1.txt
diff options
context:
space:
mode:
Diffstat (limited to 'slackware64-current/slackware64/d/gdb-7.10.1-x86_64-1.txt')
-rw-r--r--slackware64-current/slackware64/d/gdb-7.10.1-x86_64-1.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/slackware64-current/slackware64/d/gdb-7.10.1-x86_64-1.txt b/slackware64-current/slackware64/d/gdb-7.10.1-x86_64-1.txt
new file mode 100644
index 000000000..c17bdb68a
--- /dev/null
+++ b/slackware64-current/slackware64/d/gdb-7.10.1-x86_64-1.txt
@@ -0,0 +1,11 @@
+gdb: gdb (the GNU symbolic debugger)
+gdb: GDB, the GNU Project debugger, allows you to see what is going on
+gdb: inside another program while it executes -- or what another program
+gdb: was doing at the moment it crashed. GDB can do four main kinds of
+gdb: things to help you catch bugs in the act: 1) Start your program,
+gdb: specifying anything that might affect its behavior. 2) Make your
+gdb: program stop on specified conditions. 3) Examine what has happened,
+gdb: when your program has stopped. 4) Change things in your program, so
+gdb: you can experiment with correcting the effects of one bug and go on
+gdb: to learn about another. The program being debugged can be written in
+gdb: Ada, C, C++, Objective-C, Pascal and many other languages.