Lines Matching +full:on +full:- +full:the +full:- +full:go
1 # SPDX-License-Identifier: GPL-2.0-only
6 # set if architecture has the its kgdb_arch_handle_qxfer_pkt
13 depends on HAVE_ARCH_KGDB
14 depends on DEBUG_KERNEL
16 If you say Y here, it will be possible to remotely debug the
18 you also turn on the kernel config option
20 backtraces in the external debugger. Documentation of
22 as well as in Documentation/dev-tools/kgdb.rst. If
29 depends on HAVE_KPROBES
30 depends on MODULES
34 If set to Y the debug core will use the kprobe blocklist to
43 tristate "KGDB: use kgdb over the serial console"
46 depends on TTY && VT
49 Share a serial console with kgdb. Sysrq-g must be used
58 intended to for the development of new kgdb stubs
59 as well as regression testing the kgdb internals.
60 See the drivers/misc/kgdbts.c for the details about
61 the tests. The most basic of this I/O module is to boot
65 bool "KGDB: Run tests on boot"
66 depends on KGDB_TESTS
69 Run the kgdb tests on boot up automatically without the need
74 depends on KGDB_TESTS_ON_BOOT
77 This is the command string to send the kgdb test suite on
78 boot. See the drivers/misc/kgdbts.c for detailed
79 information about other strings you could use beyond the
84 depends on X86 || MIPS
87 This will add an extra call back to kgdb for the breakpoint
99 depends on KGDB_KDB
106 Alternatively the following bitmask applies:
108 0x0002 - allow arbitrary reads from memory and symbol lookup
109 0x0004 - allow arbitrary writes to memory
110 0x0008 - allow current register state to be inspected
111 0x0010 - allow current register state to be modified
112 0x0020 - allow passive inspection (backtrace, process list, lsmod)
113 0x0040 - allow flow control management (breakpoint, single step)
114 0x0080 - enable signalling of processes
115 0x0100 - allow machine to be rebooted
117 The config option merely sets the default at boot time. Both
120 override the default settings.
124 depends on VT && KGDB_KDB && !PARISC
125 depends on HAS_IOPORT
132 depends on KGDB_KDB
135 This integer controls the behaviour of kdb when the kernel gets a
138 will happen until you type 'go'.
139 CONFIG_KDB_CONTINUE_CATASTROPHIC == 0 (default). The first time
140 you type 'go', you will be warned by kdb. The secend time you type
141 'go', KDB tries to continue. No guarantees that the
144 No guarantees that the kernel is still usable in this situation.
152 If an architecture can definitely handle entering the debugger
154 Otherwise, if "kgdbwait" is passed on the kernel command line it
155 won't actually be processed until dbg_late_init() just after the
160 when early_param's are parsed, we just won't act on the
164 depending on exactly how far along the architecture has initted.