From: "Jan Beulich" <JBeulich@novell.com>
To: <linux-kernel@vger.kernel.org>
Subject: [PATCH] CONFIG_UNWIND_INFO
Date: Tue, 08 Nov 2005 13:59:38 +0100 [thread overview]
Message-ID: <4370AF4A.76F0.0078.0@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
As a foundation for reliable stack unwinding, this adds a config option
(available to all architectures except IA64) to enable the generation
of frame unwind information.
From: Jan Beulich <jbeulich@novell.com>
(actual patch attached)
[-- Attachment #2: linux-2.6.14-unwind-info.patch --]
[-- Type: application/octet-stream, Size: 1424 bytes --]
As a foundation for reliable stack unwinding, this adds a config option
(available to all architectures except IA64) to enable the generation
of frame unwind information.
From: Jan Beulich <jbeulich@novell.com>
--- 2.6.14/Makefile 2005-10-28 02:02:08.000000000 +0200
+++ 2.6.14-unwind-info/Makefile 2005-11-04 16:20:57.000000000 +0100
@@ -517,6 +517,10 @@ CFLAGS += $(call add-align,CONFIG_CC_AL
CFLAGS += $(call add-align,CONFIG_CC_ALIGN_LOOPS,-loops)
CFLAGS += $(call add-align,CONFIG_CC_ALIGN_JUMPS,-jumps)
+ifdef CONFIG_UNWIND_INFO
+CFLAGS += -fasynchronous-unwind-tables
+endif
+
ifdef CONFIG_FRAME_POINTER
CFLAGS += -fno-omit-frame-pointer $(call cc-option,-fno-optimize-sibling-calls,)
else
--- 2.6.14/lib/Kconfig.debug 2005-10-28 02:02:08.000000000 +0200
+++ 2.6.14-unwind-info/lib/Kconfig.debug 2005-11-08 10:36:39.000000000 +0100
@@ -178,3 +178,12 @@ config FRAME_POINTER
on some architectures or you use external debuggers.
If you don't debug the kernel, you can say N.
+config UNWIND_INFO
+ bool "Compile the kernel with frame unwind information"
+ depends on !IA64
+ default DEBUG_KERNEL
+ help
+ If you say Y here the resulting kernel image will be slightly larger
+ but not slower, and it will give very useful debugging information.
+ If you don't debug the kernel, you can say N, but we may not be able
+ to solve problems without frame unwind information or frame pointers.
next reply other threads:[~2005-11-08 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:59 Jan Beulich [this message]
2006-01-14 12:56 ` [PATCH] CONFIG_UNWIND_INFO Andrew Morton
2006-01-14 14:03 ` Sam Ravnborg
2006-01-16 7:36 ` Jan Beulich
2006-01-16 7:46 ` Andrew Morton
2006-01-18 11:48 ` Paul Mackerras
2006-01-18 15:18 ` Andi Kleen
2006-01-18 15:58 ` Jan Beulich
2006-01-18 16:11 ` Andi Kleen
2006-01-18 16:48 ` Jan Beulich
2006-01-20 4:47 ` Paul Mackerras
2006-01-20 6:13 ` 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=4370AF4A.76F0.0078.0@novell.com \
--to=jbeulich@novell.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