From: Eric Dumazet <dada1@cosmosbay.com>
To: Philippe Elie <phil.el@wanadoo.fr>
Cc: Andi Kleen <ak@suse.de>, Jan Beulich <JBeulich@novell.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
Date: Fri, 09 Sep 2005 14:41:06 +0200 [thread overview]
Message-ID: <432182E2.2060105@cosmosbay.com> (raw)
In-Reply-To: <20050909110702.GA787@zaniah>
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
next prev parent reply other threads:[~2005-09-09 12:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 16:04 [PATCH] allow CONFIG_FRAME_POINTER for x86-64 Jan Beulich
2005-09-09 8:54 ` [discuss] " Andi Kleen
2005-09-09 9:16 ` Jan Beulich
2005-09-09 9:23 ` Andi Kleen
2005-09-09 9:40 ` Jan Beulich
2005-09-09 10:45 ` Hugh Dickins
2005-09-09 10:58 ` Andi Kleen
2005-09-09 11:14 ` Hugh Dickins
2005-09-09 11:21 ` Andi Kleen
2005-09-09 11:31 ` Hugh Dickins
2005-09-09 11:42 ` Andi Kleen
2005-09-09 12:00 ` Hugh Dickins
2005-09-09 17:19 ` Alexander Nyberg
2005-09-10 5:13 ` Andrew Morton
2005-09-10 6:12 ` Andi Kleen
2005-09-09 11:07 ` Philippe Elie
2005-09-09 11:19 ` Andi Kleen
2005-09-09 12:41 ` Eric Dumazet [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 17:50 Chuck Ebbert
2005-09-10 0:16 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432182E2.2060105@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=JBeulich@novell.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox