From: Roland Dreier <roland@topspin.com>
To: Eli Cohen <mlxk@mellanox.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: stack dumps, CONFIG_FRAME_POINTER and i386 (was Re: sysrq shows impossible call stack)
Date: 20 Apr 2004 10:51:08 -0700 [thread overview]
Message-ID: <5265buzgfn.fsf_-_@topspin.com> (raw)
In-Reply-To: <40855F95.7080003@mellanox.co.il>
Your question prompted me to look at show_trace() in
arch/i386/kernel/traps.c. I see that even in kernels as new as 2.6.5,
there is no attempt to use frame pointers for stack dumps even when
CONFIG_FRAME_POINTER is set. I seem to remember some patches to do
this floating around a while ago. How did that discussion end up?
(Red Hat seems to have something to do this in the source for the
version of 2.4.21 that they ship in RHEL 3, but none of their shipped
kernels turn on CONFIG_FRAME_POINTER).
Thanks,
Roland
next prev parent reply other threads:[~2004-04-20 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 15:45 sysrq shows impossible call stack Eli Cohen
2004-04-20 16:26 ` Roland Dreier
2004-04-20 17:36 ` Eli Cohen
2004-04-20 17:51 ` Roland Dreier [this message]
2004-04-20 20:26 ` stack dumps, CONFIG_FRAME_POINTER and i386 (was Re: sysrq shows impossible call stack) Adam Litke
2004-04-21 0:12 ` Roland Dreier
2004-04-21 1:39 ` Andrew Morton
2004-04-21 1:41 ` Andrew Morton
2004-04-21 23:28 ` Adam Litke
2004-04-21 23:50 ` Andrew Morton
2004-04-22 18:25 ` Adam Litke
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=5265buzgfn.fsf_-_@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlxk@mellanox.co.il \
/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