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.
| OS | Architecture | Version |
|---|---|---|
| NetBSD 10.0 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 10.0 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 10.0 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 9.0 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 9.0 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 9.0 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 9.3 | x86_64 | gdb-10.1nb6.tgz |
| NetBSD 9.3 | x86_64 | gdb-10.1nb6.tgz |
Binary packages can be installed with the high-level tool pkgin (which can be installed with pkg_add) or pkg_add(1) (installed by default). The NetBSD packages collection is also designed to permit easy installation from source.
The pkg_admin audit command locates any installed package which has been mentioned in security advisories as having vulnerabilities.
Please note the vulnerabilities database might not be fully accurate, and not every bug is exploitable with every configuration.
Problem reports, updates or suggestions for this package should be reported with send-pr.