summaryrefslogtreecommitdiffstats
path: root/gnu/usr.bin/gdb/kgdb/kgdb.1
Commit message (Collapse)AuthorAgeFilesLines
* MFS11 320824: Add deprecation notices for gdb and kgdb.jhb2017-07-101-1/+11
| | | | | | | | | | Even though gdb and kgdb may not be removed for 12.0 on some architectures, the notice is unconditional as these tools will likely be removed at some point in the future when adequate replacements are available (gdb in ports or lldb in base). Approved by: re (gjb) Relnotes: yes
* kgdb enhancements!adrian2013-02-191-0/+4
| | | | | | | | | * document the kgdb -b flag * better verify what's valid with -b * add more comprehensive command line help PR: kern/175743 Submitted by: Christoph Mallon <christoph.mallon@gmx.de>
* mdoc: order prologue macros consistently by Dd/Dt/Osuqs2010-04-141-1/+1
| | | | | | | | Although groff_mdoc(7) gives another impression, this is the ordering most widely used and also required by mdocml/mandoc. Reviewed by: ru Approved by: philip, ed (mentors)
* Bump document date for the previous change.ru2006-10-211-1/+2
|
* Document '-w' from main.c rev. 1.11.obrien2006-10-111-0/+8
|
* Spell "currently" correctly.keramida2005-07-281-1/+1
|
* Implement and document the -q and -f options with their correspondingmarcel2005-03-021-2/+13
| | | | | | | long form (-quiet and -fullname resp.) Bump documentation date. PR: bin/78031 MFC after: 5 days
* .It the -v option.obrien2005-03-011-1/+1
|
* Markup nits.ru2005-01-131-4/+3
|
* Document all options and general usage.joerg2004-11-221-0/+67
| | | | | | | | | | | | Implement the -a option to bump the annotation_level. This improves the Emacs gud behaviour. You can now supply the following function (defun gud-gdb-massage-args (file args) (cons "-a" args)) (e.g. by evaluating it from the *scratch* buffer) and get the normal jump to the source window when browsing the stack. We should probably eventually supply our own kgdb submode to gud.el.
* Fix the abuse of Ar macros for designating flag options, use Fl instead.joerg2004-11-221-4/+4
|
* Improve the usage. Without any arguments, kgdb(1) works on /dev/memmarcel2004-08-151-1/+1
| | | | | | | | | with the currently running kernel image. Otherwise, one of -c, -n or -r is expected for working on a particular core file (-c), working on a saved dump (-n) or working remotely (-r). When working on a saved dump, a kernel may be omitted. For a remote debugging session (-r), kgdb(1) will use the specified device.
* Add the beginnings of kernel debugging support. the kgdb(1) toolmarcel2004-07-251-0/+50
is basicly a shell on top of libgdb that knows about kernel threads, kernel modules and kvm(3). As the word "beginnings" implies, not all of the features have been implemented yet. The tool is useful and I'd like feedback on the taken route. The simplest way to debug a kernel core file is: kgdb -n 0 This opens /var/crash/vmcore.0 with the corresponding kernel in the object directory (kernel.debug is used if it exists). Typical things that need to be added are: o Auto loading of kernel modules, o Handling of trapframes so that backtraces can be taken across them, o Some fancy commands to extract useful information out of a core file, o Various (probably many) other things.
OpenPOWER on IntegriCloud