Kconfig.debug 1.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. menu "Kernel hacking"
  2. source "lib/Kconfig.debug"
  3. config GDBSTUB
  4. bool "Remote GDB kernel debugging"
  5. depends on DEBUG_KERNEL
  6. select DEBUG_INFO
  7. select FRAME_POINTER
  8. help
  9. If you say Y here, it will be possible to remotely debug the kernel
  10. using gdb. This enlarges your kernel ELF image disk size by several
  11. megabytes and requires a machine with more than 16 MB, better 32 MB
  12. RAM to avoid excessive linking time. This is only useful for kernel
  13. hackers. If unsure, say N.
  14. choice
  15. prompt "GDB stub port"
  16. default GDBSTUB_UART1
  17. depends on GDBSTUB
  18. help
  19. Select the on-CPU port used for GDB-stub
  20. config GDBSTUB_UART0
  21. bool "/dev/ttyS0"
  22. config GDBSTUB_UART1
  23. bool "/dev/ttyS1"
  24. endchoice
  25. config GDBSTUB_IMMEDIATE
  26. bool "Break into GDB stub immediately"
  27. depends on GDBSTUB
  28. help
  29. If you say Y here, GDB stub will break into the program as soon as
  30. possible, leaving the program counter at the beginning of
  31. start_kernel() in init/main.c.
  32. config GDB_CONSOLE
  33. bool "Console output to GDB"
  34. depends on GDBSTUB
  35. help
  36. If you are using GDB for remote debugging over a serial port and
  37. would like kernel messages to be formatted into GDB $O packets so
  38. that GDB prints them as program output, say 'Y'.
  39. endmenu