linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: mmarek@suse.cz
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 2/2] Kbuild: Add a option to enable dwarf4
Date: Wed, 30 Jul 2014 01:11:33 +0200	[thread overview]
Message-ID: <1406675493-2539-2-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1406675493-2539-1-git-send-email-andi@firstfloor.org>

From: Andi Kleen <ak@linux.intel.com>

I found that a lot of unresolvable variables when using gdb on the kernel
become resolvable when dwarf4 is enabled. So add a Kconfig flag to enable it.

It definitely increases the debug information size, but on the other
hand this isn't so bad when debug fusion is used.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 Makefile          | 3 +++
 lib/Kconfig.debug | 9 +++++++++
 2 files changed, 12 insertions(+)

diff --git a/Makefile b/Makefile
index 6a717cd..6cdf3f0 100644
--- a/Makefile
+++ b/Makefile
@@ -696,6 +696,9 @@ KBUILD_CFLAGS	+= -g
 endif
 KBUILD_AFLAGS	+= -Wa,-gdwarf-2
 endif
+ifdef CONFIG_DEBUG_INFO_DWARF4
+KBUILD_CFLAGS	+= -gdwarf-4
+endif
 
 ifdef CONFIG_DEBUG_INFO_REDUCED
 KBUILD_CFLAGS 	+= $(call cc-option, -femit-struct-debug-baseonly) \
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 0360468..a2dcf97 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -158,6 +158,15 @@ config DEBUG_INFO_SPLIT
 	  to know about the .dwo files and include them.
 	  Incompatible with older versions of ccache.
 
+config DEBUG_INFO_DWARF4
+	bool "Generate dwarf4 debuginfo"
+	depends on DEBUG_INFO
+	help
+	  Generate dwarf4 debug info. This requires recent versions
+	  of gcc and gdb. It makes the debug information larger.
+	  But it significantly improves the success of resolving
+	  variables in gdb on optimized code.
+
 config ENABLE_WARN_DEPRECATED
 	bool "Enable __deprecated logic"
 	default y
-- 
1.8.5.2


  reply	other threads:[~2014-07-29 23:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 23:11 [PATCH 1/2] kbuild: Support split debug info v4 Andi Kleen
2014-07-29 23:11 ` Andi Kleen [this message]
2014-07-30 13:38   ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Michal Marek
2014-07-30 13:50 ` [PATCH 1/2] kbuild: Support split debug info v4 Michal Marek
2014-07-30 18:44   ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2014-07-15 23:16 [PATCH 1/2] kbuild: Support split debug info v3 Andi Kleen
2014-07-15 23:16 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Andi Kleen
2014-07-20 19:23   ` Sam Ravnborg
2014-07-20 21:17     ` Andi Kleen
2014-05-16 22:06 [PATCH 1/2] kbuild: Support split debug info v3 Andi Kleen
2014-05-16 22:06 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 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=1406675493-2539-2-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).