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

Philippe Elie a écrit :

On Fri, 09 Sep 2005 at 11:23 +0000, Andi Kleen wrote:

Indeed. Someone must have fixed it.  But why would anyone want frame pointers
on x86-64?

Oprofile can use it, I though it was already used but apparently only
to backtrace userspace actually.

Hi Pilippe

Last time I tried oprofile with call graph on my opteron machine (linux-2.6.13 SMP), the machine crashed instantly in dump_backtrace()

Apparently the user program was in a state were 'struct frame_head * head' was not part of the user thread stack, but some strange value like 0x8000000000xxyyzz

Eric
-
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: Andi Kleen <[email protected]>
  • Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
    • From: "Jan Beulich" <[email protected]>
  • Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
    • From: Andi Kleen <[email protected]>
  • Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
    • From: Philippe Elie <[email protected]>

• Prev by Date: Physical device to Kernel-netlink mapper
• Next by Date: Re: [PATCH] rmmod notifier chain
• Previous by thread: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
• Next by thread: [PATCH] adjust x86-64 HPET definitions
• 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]