| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 3 Debugging kernel and modules via gdb
53 - Start gdb: gdb vmlinux
56 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add::
72 (gdb) lx-symbols
92 (gdb) c
107 (gdb) lx-dmesg
158 List of commands and functions
161 The number of commands and convenience functions may evolve over the time,
162 this is just a snapshot of the initial version::
164 (gdb) apropos lx
[all …]
|
| H A D | kgdb.rst | 273 on the initial connect, or to use a debugger proxy that allows an
425 list of the commands that are available.
427 Some useful commands in kdb include:
626 shell looks for the typical first commands that gdb would issue with the
627 gdb remote protocol and if it sees one of those commands it
639 Running kdb commands from gdb
642 It is possible to run a limited set of kdb commands from gdb, using the
646 operations if you have gdb connected. The more useful commands to run
648 information commands. To see all the kdb commands you can run
758 - A registration API to register additional kdb shell commands.
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 3 Debugging kernel and modules via gdb
53 - Start gdb: gdb vmlinux
56 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add::
72 (gdb) lx-symbols
92 (gdb) c
107 (gdb) lx-dmesg
158 List of commands and functions
161 The number of commands and convenience functions may evolve over the time,
162 this is just a snapshot of the initial version::
164 (gdb) apropos lx
[all …]
|
| H A D | kgdb.rst | 273 on the initial connect, or to use a debugger proxy that allows an
425 list of the commands that are available.
427 Some useful commands in kdb include:
626 shell looks for the typical first commands that gdb would issue with the
627 gdb remote protocol and if it sees one of those commands it
639 Running kdb commands from gdb
642 It is possible to run a limited set of kdb commands from gdb, using the
646 operations if you have gdb connected. The more useful commands to run
648 information commands. To see all the kdb commands you can run
758 - A registration API to register additional kdb shell commands.
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 3 Debugging kernel and modules via gdb
53 - Start gdb: gdb vmlinux
56 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add::
72 (gdb) lx-symbols
92 (gdb) c
107 (gdb) lx-dmesg
158 List of commands and functions
161 The number of commands and convenience functions may evolve over the time,
162 this is just a snapshot of the initial version::
164 (gdb) apropos lx
[all …]
|
| H A D | kgdb.rst | 273 on the initial connect, or to use a debugger proxy that allows an
425 list of the commands that are available.
427 Some useful commands in kdb include:
626 shell looks for the typical first commands that gdb would issue with the
627 gdb remote protocol and if it sees one of those commands it
639 Running kdb commands from gdb
642 It is possible to run a limited set of kdb commands from gdb, using the
646 operations if you have gdb connected. The more useful commands to run
648 information commands. To see all the kdb commands you can run
758 - A registration API to register additional kdb shell commands.
[all …]
|
| /dports/devel/bashdb/bashdb-5.0-1.1.2/ |
| H A D | NEWS.md | 249 * autoeval mode added: if set, commands that aren't debugger commands are
268 * Add set/show trace-commands to make the same as gdb 6.6
269 * show commands now allows for a starting number and +, same as gdb
302 * Add gdb-like "signal" command
322 * Add gdb 'commands' command:
331 * source line preserving initial indentation
358 Version 3.1 0.04 (initial 3.1 release)
410 done a cd. Save initial cwd.
481 * Make breakpoint output more like gdb's. make show output more like gdb's
625 * Add gdb's:
[all …]
|
| /dports/devel/kdbg/kdbg-kdbg-3.0.0/ |
| H A D | ChangeLog-pre-2.2.0 | 28 an initial fix.
89 Matthew Allen for the initial code).
131 "Orphaned breakpoints", i.e. breakpoints that gdb cannot set
155 initial code).
246 Watchpoints. Finally! (On Linux/i386 works best with gdb 5!)
268 multi-threaded programs, like gdb 5.
282 By default, do not log communication with gdb.
348 for gdb 4.18.
360 Fixed cases where gdb commands where executed after debuggee has exited.
362 Do not execute gdb commands after an interrupt.
[all …]
|
| /dports/devel/xxgdb/xxgdb-1.12/ |
| H A D | xxgdb.1 | 9 xxgdb - X window system interface to the gdb debugger.
23 _X_x_g_d_b allows initial gdb commands stored in the file
32 information for gdb.
49 default "gdb"
55 (eg, "(gdb) ").
277 yes Send 'y' (yes) to gdb. To be used when gdb requires a
280 no Send 'n' (no) to gdb. To be used when gdb requires a
428 The name of the debugger program. ("gdb")
440 .gdbinit local initial commands file
441 ~/.gdbinit user's initial commands file
[all …]
|
| /dports/editors/emacs/emacs-27.2/doc/emacs/ |
| H A D | building.texi | 453 initial default for the command---one that runs both @code{find} and
469 These commands build the shell commands based on the variables
609 using the minibuffer. The minibuffer's initial contents contain the
632 @kbd{M-x gud-gdb} and other commands listed in
647 commands to repeat them.
932 gdb}.
1361 execution control commands.
1391 commands may be added in the future.
1653 unconditionally resets the variable to the initial value specified by
1703 @vindex initial-scratch-message
[all …]
|
| /dports/editors/emacs-devel/emacs-4d1968b/doc/emacs/ |
| H A D | building.texi | 421 can chain @command{grep} commands, like this:
461 initial default for the command---one that runs both @code{find} and
477 These commands build the shell commands based on the variables
617 using the minibuffer. The minibuffer's initial contents contain the
640 @kbd{M-x gud-gdb} and other commands listed in
655 commands to repeat them.
1400 execution control commands.
1430 commands may be added in the future.
1686 initial value specified by the @code{defvar}; this is convenient for
1747 @vindex initial-scratch-message
[all …]
|
| /dports/devel/gdb/gdb-11.1/gdb/doc/ |
| H A D | gdb.info-5 | 2114 multiple words, then the initial words are looked for as prefix
2367 [#:initial-value initial-value])
2370 consists of multiple words, then the initial words are looked for
2429 The argument INITIAL-VALUE specifies the initial value of the
2431 '<gdb:parameter>' object and its result is used as the initial
2432 value of the parameter. The initial value must be valid for the
4938 The initial working directory of GDB is printed on the top line of
5870 '=tsv-created,name=NAME,initial=INITIAL'
5872 initial value INITIAL.
5879 '=tsv-modified,name=NAME,initial=INITIAL[,current=CURRENT]'
[all …]
|
| H A D | guile.texi | 53 @cindex guile commands
1727 There is no support for multi-line commands, that is commands that
1734 multiple words, then the initial words are looked for as prefix
1735 commands. In this case, if one of the prefix commands does not exist,
1776 list of commands.
1869 commands in the on-line help system; note that prefix commands are not
1934 a list of commands in this category, as well as the list of gdb macros
2024 consists of multiple words, then the initial words are looked for as prefix
2085 The argument @var{initial-value} specifies the initial value of the parameter.
2087 object and its result is used as the initial value of the parameter.
[all …]
|
| H A D | gdb.info-4 | 518 file where GDB reads an initial command history list, and where it
600 'show commands'
941 gdb-scripts: Auto-loading of canned sequences of commands scripts is on.
1106 commands:
1207 auto-load: Loading canned sequences of commands script "/tmp/true-gdb.gdb"
1303 commands.
1765 >echo command initial def\n
2810 When implementing GDB commands in Python via 'gdb.Command', or
4076 of each 'gdb.Frame' in commands where frame filters are executed. This
5637 words, then the initial words are looked for as prefix commands.
[all …]
|
| H A D | ChangeLog | 702 commands.
963 commands.
1273 commands.
1954 commands.
2011 commands.
2601 commands.
2918 * gdb.texinfo (Symbols): Document new commands
3896 commands.
3937 commands.
4667 gdb commands.
[all …]
|
| /dports/devel/gdb761/gdb-7.6.1/gdb/doc/ |
| H A D | gdb.info-3 | 764 To start `gdbserver' without supplying an initial command to run or
1096 auto-retry is enabled, if the initial attempt to connect fails,
1432 your program doesn't keep hitting the initial breakpoint instead
1983 examine the initial instructions of the function in order to skip the
3605 the file where GDB reads an initial command history list, and
3876 gdb-scripts: Auto-loading of canned sequences of commands scripts is on.
4032 of commands (*note Sequences::), as long as `set auto-load gdb-scripts'
4187 auto-load: Loading canned sequences of commands script "/tmp/true-gdb.gdb"
5367 When implementing GDB commands in Python via `gdb.Command', it is
6537 words, then the initial words are looked for as prefix commands.
[all …]
|
| H A D | gdb.info-4 | 1313 The initial working directory of GDB is printed on the top line of
2138 `=tsv-created,name=NAME,initial=INITIAL'
2140 initial value INITIAL.
2147 `=tsv-modified,name=NAME,initial=INITIAL[,current=CURRENT]'
2149 initial value INITIAL. The current value CURRENT of trace state
5768 specified, sets the initial value of the specified trace variable to
5790 `initial'
5791 The initial value. This is a 64-bit signed integer. This field
5813 {width="11",alignment="-1",col_name="initial",colhdr="Initial"},
5815 body=[variable={name="$trace_timestamp",initial="0"}
[all …]
|
| H A D | ChangeLog | 369 * gdb.texinfo (Python Commands): Document the new commands.
537 gdb commands.
1021 in main. Mention the need to get past the initial breakpoint.
2276 commands.
2611 commands.
3269 * gdb.texinfo: Add nexti to list of commands that support
3313 commands.
3895 commands.
3988 commands.
5915 * gdb.texinfo (TUI Commands): Document tui reg commands.
[all …]
|
| H A D | gdb.info-2 | 80 Words (four bytes). This is the initial default.
1171 initial `$'.
1749 For the sake of printing this manual, let's use ASCII as our initial
2162 tailcall: initial: 0x4004d2(a) 0x4004ce(b) 0x4004b2(c) 0x4004a2(d)
2174 `initial:' state shows some random possible calling sequence GDB has
2797 `$NAME', and optionally gives it an initial value of EXPRESSION.
2802 supplied initial value to the existing variable of that name,
2803 overwriting any previous initial value. The default initial value
7167 commands:
7548 significant bit of each byte first. The initial pattern `0xffffffff'
[all …]
|
| /dports/devel/avr-gdb/gdb-7.3.1/gdb/doc/ |
| H A D | gdb.info-3 | 264 commands.
596 examine the initial instructions of the function in order to skip the
743 commands.
1698 commands.
2048 commands:
2190 the file where GDB reads an initial command history list, and
2503 commands.
3492 When implementing GDB commands in Python via `gdb.Command', it is
4485 words, then the initial words are looked for as prefix commands.
4703 multiple words, then the initial words are looked for as prefix
[all …]
|
| H A D | gdb.info-2 | 181 initial `$'.
692 For the sake of printing this manual, let's use ASCII as our initial
1548 `$NAME', and optionally gives it an initial value of EXPRESSION.
1553 supplied initial value to the existing variable of that name,
1554 overwriting any previous initial value. The default initial value
1558 List all the trace state variables along with their initial values.
5826 part of PATH following the initial `remote:' (if present) is used
6093 significant bit of each byte first. The initial pattern `0xffffffff'
6106 initially supplied `crc' argument means that an initial call to this
6823 To start `gdbserver' without supplying an initial command to run or
[all …]
|
| /dports/devel/cgdb/cgdb-0.8.0/ |
| H A D | NEWS | 3 * Fix issue #298 - CGDB now exits when gdb exits
54 gdb window #121
119 * Status bar commands and gdb console commands now both show gdb
120 output in the gdb window (instead of only the gdb console commands).
183 * Add an initial Rust syntax highlighter.
323 * Added some new cgdb commands.
333 put these commands in your cgdbrc file,
533 * CGDB now supports getting the initial line, as well as the initial
535 determine the initial file.
724 user ran a command file through gdb on init and the file instructed gdb
[all …]
|
| /dports/lang/snobol4/snobol4-2.2.2/doc/ |
| H A D | sdb.1.pea | 10 fone) of B<gdb>(1), The GNU debugger. B<sdb>(1) uses B<readline>(3)
19 =item B<commands> I<BREAKPOINT_NUMBER>
20 Add sdb commands to execute (ie; print & continue) to a breakpoint.
59 Read sdb commands from file.
71 Non-ambiguous abbreviations of commands can be used (ie; B<s>, B<n>).
89 initial command file, read on startup.
98 B<snobol4>(1), B<gdb>(1), B<readline>(3), B<snobol4readline>(3)
129 ``quit'' and ``run'' commands say program is running even if first
|
| /dports/devel/zpu-binutils/zpu-toolchain-1.0/toolchain/gdb/gdb/doc/ |
| H A D | gdb.info-2 | 1171 commands:
2373 commands.
2652 examine the initial instructions of the function in order to skip the
2953 `(gdb)'. Use two special commands to begin your debugging session:
3474 commands.
3731 the file where GDB reads an initial command history list, and
3784 `show commands'
3791 Print ten commands just after the commands last printed.
4657 commands.
4867 The initial working directory of GDB is printed on the top line of
[all …]
|
| /dports/devel/zpu-gcc/zpu-toolchain-1.0/toolchain/gdb/gdb/doc/ |
| H A D | gdb.info-2 | 1171 commands:
2373 commands.
2652 examine the initial instructions of the function in order to skip the
2953 `(gdb)'. Use two special commands to begin your debugging session:
3474 commands.
3731 the file where GDB reads an initial command history list, and
3784 `show commands'
3791 Print ten commands just after the commands last printed.
4657 commands.
4867 The initial working directory of GDB is printed on the top line of
[all …]
|