title: How do I find Linux config options in menuconfig?
body: <p>Various web pages tell me that to get full truthful stack backtraces in the Linux kernel, I need to set <code>CONFIG_FRAME_POINTER=y</code> in my .config file. So I run <code>make menuconfig</code> and try to find it in there, but it's hardly intuitive where to navigate to do so. I search the web and find lots of pages that say to enable it, but no pages that tell me what menu options to drill down into in order to do so. So I think maybe I could run <code>make config</code> and just hit [Enter] a million times to select the current configuration choice for everything, then copy-paste the whole command window buffer contents into a text file &amp; search (case insensitive) for "frame_pointer" or "frame pointer", but still no luck; apparently I'd have to select 'y' for some submenu to even drill down to wherever it is.</p>
  
  <p>How can I find such options in config or menuconfig? Is there an option configuration hierarchy listed somewhere?</p>
  
  <p><strong>Update:</strong></p>
  
  <p>I'm using Linux Kernel v2.6.30.4-uc0; that's what I'm given with the Lantronix XPort Pro SDK. </p>
  
  <p>Based on answers I got, I use the <code>/</code> search option (not sure how I missed that before), but I'm not really able to get much farther. When I search for "FRAME_POINTER" this is what I see:</p>
  
  <pre><code>Symbol: ARCH_WANT_FRAME_POINTERS [=n]
  
  Symbol: FRAME_POINTER [=n]
   Prompt: Compile the kernel with frame pointers
     Defined at lib/Kconfig.debug:620
     Depends on: DEBUG_KERNEL &amp;&amp; (CRIS || M68K || M68KNOMMU || FRV || UML || AVR32 || SUPERH || BLACKFIN || MN10300) || ARCH_WANT_FRAME_POINTERS
     Location:
       -&gt; Kernel hacking
     Selected by: LOCKDEP &amp;&amp; DEBUG_KERNEL &amp;&amp; TRACE_IRQFLAGS_SUPPORT &amp;&amp; STACKTRACE_SUPPORT &amp;&amp; LOCKDEP_SUPPORT &amp;&amp; !MIPS &amp;&amp; !PPC &amp;&amp; !ARM_UNWIND &amp;&amp; !S390 || FAULT_INJECTION_STACKTRACE_FILTER &amp;&amp; FAULT_INJECTION_
  </code></pre>
  
  <p>Note that the "Selected by:" line is longer than what I can see, even when I stretch the <code>make menuconfig</code> window as wide as the whole screen, and there's no option I can find to scroll the text to see it all. Very frustrating, as most of this ordeal has been. BTW, thanks a lot to whomever saw fit to downvote without leaving a helpful comment.</p>
  
  <p><strong><em>So I try to navigate to this option using the "search" information above, but it's still nowhere to be found!</em></strong></p>
  
  <p>When I go to the <code>Kernel hacking ---&gt;</code> menu, there is no choice to enable stack frames. There is also no menu choice "Compile-time checks and compiler options" as indicated in @ShantanuAde's answer. I see these choices:</p>
  
  <pre><code>------- Kernel hacking -------------------------
  [ ] Show timing information on printks
  [ ] Enable __deprecated logic
  [ ] Enable __must_check logic
  (1024) Warn for stack frames larger than (needs gcc 4.4)
  [ ] Magic SysRq key
  [ ] Enable unused/obsolete exported symbols
  [ ] Debug Filesystem
  [ ] Run 'make headers_check' when building vmlinux
  [ ] Kernel debugging
  [ ] Debug memory initialisation
  [ ] Check for stalled CPUs delaying RCU grace periods
  [ ] Sysctl checks
  [ ] Sample kernel code  ---&gt;
  [ ] Full Symbolic/Source Debugging support
  [ ] Use fast second timer for profiling
  [ ] Compiled-in Kernel Boot Parameter
  [ ] Suppress Kernel BUG Messages
  </code></pre>
  
  <p>The only thing I can think of that might get me closer to CONFIG_FRAME_POINTER is "Kernel debugging" but when I turn that on, the only extra options I get are:</p>
  
  <pre><code>[*] Kernel debugging
  [ ]   Debug shared IRQ handlers (NEW)
  [*]   Detect Soft Lockups (NEW)
  [ ]     Panic (Reboot) On Soft Lockups (NEW)
  [*]   Detect Hung Tasks (NEW)
  [ ]     Panic (Reboot) On Hung Tasks (NEW)
  [*]   Collect scheduler debugging info (NEW)
  [ ]   Collect scheduler statistics (NEW)
  [ ]   Collect kernel timers statistics (NEW)
  [ ]   Debug object operations (NEW)
  [ ]   Debug slab memory allocations (NEW)
  [ ] Spinlock and rw-lock debugging: basic checks (NEW)
  [ ] Mutex debugging: basic checks (NEW)
  [ ] Spinlock debugging: sleep-inside-spinlock checking (NEW)
  [ ] Locking API boot-time self-tests (NEW)
  [ ] kobject debugging (NEW)
  [ ] Verbose BUG() reporting (adds 70K) (NEW)
  [ ] Compile the kernel with debug info (NEW)
  [ ] Debug VM (NEW)
  [ ] Debug the global anon/private NOMMU mapping region tree (NEW)
  [ ] Debug filesystem writers count (NEW)
  </code></pre>
  
  <p>Very, very frustrating. And it doesn't help when jerks downvote without leaving any helpful info.</p>