From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Bradley Chapman <kakadu_croc@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What do frame pointers do?
Date: Sun, 2 Nov 2003 20:45:56 -0800 [thread overview]
Message-ID: <20031102204556.0c5b377a.rddunlap@osdl.org> (raw)
In-Reply-To: <20031102170029.59013.qmail@web40908.mail.yahoo.com>
On Sun, 2 Nov 2003 09:00:29 -0800 (PST) Bradley Chapman <kakadu_croc@yahoo.com> wrote:
| What exactly is the purpose of a frame pointer? As far back as I can remember, 2.4
| and 2.6 kernels have supported something called a frame pointer, which slows down
| the kernel slightly but supposedly outputs 'very useful debugging information.'
| Unfortunately, it doesn't really explain what they are, and for the past few months,
| I haven't seen any hacker gods asking for CONFIG_FRAME_POINTER=y, except for Russell
| King, who wants them compiled for ARM processors for some reason (I grepped the
| kernel source looking for answers and found a comment which implied this).
|
| Does anyone know where I can find a good explanation of what they are and what they
| do?
Frame pointers enable more deterministic back tracing of the stack,
which can be helpful for tracking down bugs. I build with
CONFIG_FRAME_POINTER enabled all of the time.
Note, however, that current 2.6.x Makefile does not allow frame pointers
to be used with gcc 2.96 since it has some known problems with code generation
when using frame pointers.
There is a little discussion of frame pointers in the Intel
IA-32 Intel® Architecture Software Developer;s Manual Volume 1:
Basic Architecture
and
IA-32 Intel® Architecture Software Developer's Manual Volume 2:
Instruction Set Reference,
which are downloadable as .pdf files from developer.intel.com.
--
~Randy
next prev parent reply other threads:[~2003-11-03 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 17:00 Bradley Chapman
2003-11-03 4:45 ` Randy.Dunlap [this message]
2003-11-03 9:29 ` Bradley Chapman
2003-11-03 10:04 ` Russell King
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=20031102204556.0c5b377a.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=kakadu_croc@yahoo.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
all inboxes | Powered by JetHome®