public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Andrew Morton <akpm@osdl.org>, Alexander Nyberg <alexn@telia.com>,
	hugh@veritas.com, JBeulich@novell.com,
	linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
Date: Sat, 10 Sep 2005 08:12:54 +0200	[thread overview]
Message-ID: <200509100812.55384.ak@suse.de> (raw)
In-Reply-To: <20050909221320.6b53a030.akpm@osdl.org>

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


  reply	other threads:[~2005-09-10  6:13 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 [this message]
2005-09-09 11:07       ` Philippe Elie
2005-09-09 11:19         ` Andi Kleen
2005-09-09 12:41         ` Eric Dumazet
  -- 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=200509100812.55384.ak@suse.de \
    --to=ak@suse.de \
    --cc=JBeulich@novell.com \
    --cc=akpm@osdl.org \
    --cc=alexn@telia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox