Re: [PATCH] CONFIG_UNWIND_INFO

>The usual use case is that you only need it on disk for your gdb,
>but not in RAM.

If you care about gdb, you'd be building with CONFIG_DEBUG_INFO anyway, and get the same information in .debug_frames
(which already is a noload section) without the need to enable CONFIG_UNWIND_INFO.

Jan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH] CONFIG_UNWIND_INFO
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] CONFIG_UNWIND_INFO
    • From: "Jan Beulich" <[email protected]>
  • Re: [PATCH] CONFIG_UNWIND_INFO
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: [patch 1/2] atomic_add_unless sadness
• Next by Date: Re: FYI: RAID5 unusably unstable through 2.6.14
• Previous by thread: Re: [PATCH] CONFIG_UNWIND_INFO
• Next by thread: Re: [PATCH] CONFIG_UNWIND_INFO
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]