summaryrefslogblamecommitdiff
path: root/lib/Kconfig.kgdb
blob: 43cb93fa2651263930ae6c0f8181cd43aa119052 (plain) (tree) 
dc7d55270521 ^

e024cbd257ef ^



dc7d55270521 ^

dcc7871128e9 ^

dc7d55270521 ^




5f5ddfb3605d ^







dc7d55270521 ^

e024cbd257ef ^

dc7d55270521 ^



dc7d55270521 ^






e8d31c204e36 ^



e8d31c204e36 ^









974460c5bfd9 ^


















e024cbd257ef ^

f503b5ae53cb ^


5dd11d5d47d2 ^

f503b5ae53cb ^






dcc7871128e9 ^






ada64e4c98eb ^







e024cbd257ef ^

1

2
3
4

5

6

7
8
9
10

11
12
13
14
15
16
17

18

19

20
21
22

23
24
25
26
27
28

29
30
31

32
33
34
35
36
37
38
39
40

41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

59

60
61

62

63
64
65
66
67
68

69
70
71
72
73
74

75
76
77
78
79
80
81

82

 


                     
               
                                    



                                                                      






                                                                      
 
       


                                                         





                                                                


                                        








                                                                  

















                                                                      
 

                                                           
                             





                                                                    





                                                      






                                                              
            

config HAVE_ARCH_KGDB
	bool

menuconfig KGDB
	bool "KGDB: kernel debugger"
	depends on HAVE_ARCH_KGDB
	depends on DEBUG_KERNEL && EXPERIMENTAL
	help
	  If you say Y here, it will be possible to remotely debug the
	  kernel using gdb.  It is recommended but not required, that
	  you also turn on the kernel config option
	  CONFIG_FRAME_POINTER to aid in producing more reliable stack
	  backtraces in the external debugger.  Documentation of
	  kernel debugger is available at http://kgdb.sourceforge.net
	  as well as in DocBook form in Documentation/DocBook/.  If
	  unsure, say N.

if KGDB

config KGDB_SERIAL_CONSOLE
	tristate "KGDB: use kgdb over the serial console"
	select CONSOLE_POLL
	select MAGIC_SYSRQ
	default y
	help
	  Share a serial console with kgdb. Sysrq-g must be used
	  to break in initially.

config KGDB_TESTS
	bool "KGDB: internal test suite"
	default n
	help
	  This is a kgdb I/O module specifically designed to test
	  kgdb's internal functions.  This kgdb I/O module is
	  intended to for the development of new kgdb stubs
	  as well as regression testing the kgdb internals.
	  See the drivers/misc/kgdbts.c for the details about
	  the tests.  The most basic of this I/O module is to boot
	  a kernel boot arguments "kgdbwait kgdbts=V1F100"

config KGDB_TESTS_ON_BOOT
	bool "KGDB: Run tests on boot"
	depends on KGDB_TESTS
	default n
	help
	  Run the kgdb tests on boot up automatically without the need
	  to pass in a kernel parameter

config KGDB_TESTS_BOOT_STRING
	string "KGDB: which internal kgdb tests to run"
	depends on KGDB_TESTS_ON_BOOT
	default "V1F100"
	help
	  This is the command string to send the kgdb test suite on
	  boot.  See the drivers/misc/kgdbts.c for detailed
	  information about other strings you could use beyond the
	  default of V1F100.

config KGDB_LOW_LEVEL_TRAP
       bool "KGDB: Allow debugging with traps in notifiers"
       depends on X86 || MIPS
       default n
       help
         This will add an extra call back to kgdb for the breakpoint
         exception handler on which will will allow kgdb to step
         through a notify handler.

config KGDB_KDB
	bool "KGDB_KDB: include kdb frontend for kgdb"
	default n
	help
	  KDB frontend for kernel

config KDB_KEYBOARD
	bool "KGDB_KDB: keyboard as input device"
	depends on VT && KGDB_KDB
	default n
	help
	  KDB can use a PS/2 type keyboard for an input device

endif # KGDB