Kconfig.debug 1.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. menu "Kernel hacking"
  2. source "lib/Kconfig.debug"
  3. config CMDLINE_ON_HOST
  4. bool "Show command line arguments on the host in TT mode"
  5. depends on MODE_TT
  6. default !DEBUG_INFO
  7. help
  8. This controls whether arguments in guest processes should be shown on
  9. the host's ps output.
  10. Enabling this option hinders debugging on some recent GDB versions
  11. (because GDB gets "confused" when we do an execvp()). So probably you
  12. should disable it.
  13. config PT_PROXY
  14. bool "Enable ptrace proxy"
  15. depends on XTERM_CHAN && DEBUG_INFO && MODE_TT
  16. help
  17. This option enables a debugging interface which allows gdb to debug
  18. the kernel without needing to actually attach to kernel threads.
  19. If you want to do kernel debugging, say Y here; otherwise say N.
  20. config GPROF
  21. bool "Enable gprof support"
  22. depends on DEBUG_INFO && MODE_SKAS && !MODE_TT
  23. help
  24. This allows profiling of a User-Mode Linux kernel with the gprof
  25. utility.
  26. See <http://user-mode-linux.sourceforge.net/gprof.html> for more
  27. details.
  28. If you're involved in UML kernel development and want to use gprof,
  29. say Y. If you're unsure, say N.
  30. config GCOV
  31. bool "Enable gcov support"
  32. depends on DEBUG_INFO && MODE_SKAS
  33. help
  34. This option allows developers to retrieve coverage data from a UML
  35. session.
  36. See <http://user-mode-linux.sourceforge.net/gprof.html> for more
  37. details.
  38. If you're involved in UML kernel development and want to use gcov,
  39. say Y. If you're unsure, say N.
  40. endmenu