From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Hugh Dickins <hugh@veritas.com>,
Jan Beulich <JBeulich@novell.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
Date: Sat, 10 Sep 2005 02:16:45 +0200 [thread overview]
Message-ID: <200509100216.46247.ak@suse.de> (raw)
In-Reply-To: <200509091351_MC3-1-A9A7-F01A@compuserve.com>
On Friday 09 September 2005 19:50, Chuck Ebbert wrote:
> In-Reply-To: <Pine.LNX.4.61.0509091208350.6247@goblin.wat.veritas.com>
>
> On Fri, 9 Sep 2005 at 12:14:38 +0100 (BST), Hugh Dickins wrote:
> > On Fri, 9 Sep 2005, Andi Kleen wrote:
> > > It won't give more accurate backtraces, not even on i386 because
> > > show_stack doesn't have any code to follow frame pointers.
> >
> > Ah, right.
>
> What's this for, then? (arch/i386/kernel/traps.c line 116)
Ok someone added it when I wasn't looking. It certainly wasn't there some time
ago. However the point stands that x86-64 doesn't have such code.
-Andi
next prev parent reply other threads:[~2005-09-10 0:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 17:50 [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64 Chuck Ebbert
2005-09-10 0:16 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-08 16:04 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
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=200509100216.46247.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=JBeulich@novell.com \
--cc=discuss@x86-64.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.