[Bug 183024] textdump(4) mentions call doadump, should be textdump dump

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183024

Oleksandr Tymoshenko <gonzo at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|doc at FreeBSD.org             |bugs at FreeBSD.org
                 CC|                            |doc at FreeBSD.org
          Component|Documentation               |Manual Pages

sigsys at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sigsys at gmail.com

--- Comment #2 from sigsys at gmail.com ---
There's another problem with the textdump(4) example configuration.  At some
point doadump() was modified to take a boolean argument that indicates if
textdumps should be attempted at all (if it is 0, it won't do a textdump even
if textdump_pending is set).

I had a computer that used to do textdumps correctly that one day did not when
it paniced.  IIUC ddb(4)'s "call" ends up passing stack garbage when arguments
are not initialized.  And it must usually have had a non-zero value for the
first argument but this time it ended up being zero.

Both share/man/man4/textdump.4 and sbin/ddb/ddb.conf should be modified with
"call doadump(1)" or "textdump dump" (in the later case, "textdump set" would
be superfluous).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.