- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

remove duplicate semicolons where possible.

Approved by: cperciva
MFC after: 1 week

Correct subcommand name 'unset' -> 'unscript'.

Plug an fd leak

Always assign WARNS using ?=

- fix some nearby style bugs
- include Makefile.inc where it makes sense and reduces duplication

Approved by: ed (co-mentor)

Ensure 'kvm' is always initialized. If "-M" was not specified and the
garbage value on the stack was not zero, then 'ddb capture' would try to
use the garbage value as a kvm_t pointer.

MFC after: 1 week

When extracting the capture buffer from a crashdump, only read the valid
portion of the capture buffer (db_capture_bufoff vs db_capture_bufsize).
This could result in outputting garbage (e.g. lots of 'p' characters if
DIAGNOSTIC is enabled) after the end of the capture buffer. While here,
fix a spelling nit.

Reported by: Mikolaj Golub to my trociny of gmail
MFC after: 3 days

Apply various fixes:

Silence mdoc(7) warnings;
Xref correct manual pages;
Point user to the ddb.8 manual page.

PR: 129398
Submitted by: gavin

DDB scripting, textdumps, output capture, etc, all will appear in
FreeBSD 7.1 before 8.0 ships.

Spotted by: Ulrich Spoerlein <uspoerlein at gmail dot com>
MFC after: 3 days

Add "ddb capture print" and "ddb capture status" commands do ddb(8),
alowing the DDB output capture buffer to be easily extracted from
user space. Both of these commands include -M/-N arguments, allowing
them to be used with kernel crash dumps (or /dev/mem).

This makes it easier to use DDB scripting and output capture with
minidumps or full dumps rather than with text dumps, allowing DDB
output (scripted or otherwise) to be easily extracted from a crash
dump.

MFC after: 1 week
Discussed with: brooks, jhb

- Normalize usage(), add "ddb pathname" syntax.
- Revise the manpage.

Add the ability to read a file of commands to ddb(8) modeled after the
feature in ipfw(8).

Minor formatting tweaks.

Point at ddb(4) and textdump(4) man pages for more script examples.

MFC after: 3 months

Add command-line tool ddb(8), which allows DDB(4) scripts to be
managed from userspace. It is largely a wrapper for sysctl()
calls, but because the sysctls for adding and removing scripts
are awkward to use directly, this provides an easier-to-use
interface.

MFC after: 3 months