Version:  2.0.40 2.2.26 2.4.37 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16

Linux/arch/frv/Kconfig.debug

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

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us