GDB_WAIT: Clarify Kconfig description
The user has to know in which stage gdb is waiting to be able to use symbolic debugging. Change-Id: Ia992e7a2077b92c45546ae56c5fb648775f8f63b Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> Reviewed-on: https://review.coreboot.org/12709 Tested-by: build bot (Jenkins) Reviewed-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Reviewed-by: Nico Huber <nico.h@gmx.de>
This commit is contained in:
parent
b7fa7fbbd7
commit
7d234f2e69
|
@ -673,11 +673,12 @@ config GDB_STUB
|
|||
See src/arch/x86/lib/c_start.S for details.
|
||||
|
||||
config GDB_WAIT
|
||||
bool "Wait for a GDB connection"
|
||||
bool "Wait for a GDB connection in the ramstage"
|
||||
default n
|
||||
depends on GDB_STUB
|
||||
help
|
||||
If enabled, coreboot will wait for a GDB connection.
|
||||
If enabled, coreboot will wait for a GDB connection in the ramstage.
|
||||
|
||||
|
||||
config FATAL_ASSERTS
|
||||
bool "Halt when hitting a BUG() or assertion error"
|
||||
|
|
Loading…
Reference in New Issue