Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64

On Saturday 10 September 2005 07:13, Andrew Morton wrote:

> show_trace() uses print_context_stack(), but show_stack() just does a
> dump-everything.  I wondered why the CONFIG_FRAME_POINTER oops traces were
> still so crappy.   TIA ;)

It's a good thing - it wouldn't have any chance to get beyond the exception
frame.

-Andi

-
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:
  • [PATCH] allow CONFIG_FRAME_POINTER for x86-64
    • From: "Jan Beulich" <[email protected]>
  • Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
    • From: Alexander Nyberg <[email protected]>
  • Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: PCI bug in 2.6.13
• Next by Date: Re: 2.6.13-mm2
• Previous by thread: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
• Next by thread: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
• Index(es):
  • Date
  • Thread

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