From: John Garry <john.garry@huawei.com>
To: <will@kernel.org>, <catalin.marinas@arm.com>,
<linux-arm-kernel@lists.infradead.org>, <arnd@arndb.de>,
<olof@lixom.net>, <soc@kernel.org>
Cc: <jpoimboe@kernel.org>, <linux-kernel@vger.kernel.org>,
John Garry <john.garry@huawei.com>
Subject: [PATCH 2/2] arm64: defconfig: Enable DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT
Date: Mon, 25 Jul 2022 00:43:24 +0800 [thread overview]
Message-ID: <1658681004-132191-3-git-send-email-john.garry@huawei.com> (raw)
In-Reply-To: <1658681004-132191-1-git-send-email-john.garry@huawei.com>
Since commit f9b3cd245784 ("Kconfig.debug: make DEBUG_INFO selectable
from a choice") faddr2line has stopped working by default as it relies
on CONFIG_DEBUG_INFO.
Enable CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT to get it working again,
which seems the sensible config option to use.
Signed-off-by: John Garry <john.garry@huawei.com>
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index de662de0bb4d..43e3550afa45 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -1311,6 +1311,7 @@ CONFIG_CRYPTO_DEV_HISI_TRNG=m
CONFIG_CMA_SIZE_MBYTES=32
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_KERNEL=y
+CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_FS=y
# CONFIG_SCHED_DEBUG is not set
--
2.35.3
next prev parent reply other threads:[~2022-07-24 16:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 16:43 [PATCH 0/2] arm64 defconfig: Get faddr2line working John Garry
2022-07-24 16:43 ` [PATCH 1/2] arm64: defconfig: Sync with savedefconfig John Garry
2022-07-24 16:43 ` John Garry [this message]
2022-07-24 20:35 ` [PATCH 0/2] arm64 defconfig: Get faddr2line working Arnd Bergmann
2022-07-25 6:50 ` John Garry
2022-07-25 7:08 ` Arnd Bergmann
2022-07-25 11:57 ` John Garry
2022-07-25 12:51 ` Arnd Bergmann
2022-07-25 14:03 ` John Garry
2022-07-25 14:22 ` Arnd Bergmann
2022-07-25 17:39 ` John Garry
2022-07-28 8:06 ` John Garry
2022-07-28 8:23 ` Arnd Bergmann
2022-07-28 8:53 ` Srinivas Kandagatla
2022-07-28 9:09 ` Arnd Bergmann
2022-07-28 11:57 ` Jonathan Marek
2022-07-28 12:03 ` Arnd Bergmann
2022-08-04 10:35 ` soundwire qcom slimbus dependency (was Re: [PATCH 0/2] arm64 defconfig: Get faddr2line working) John Garry
2022-08-09 8:28 ` John Garry
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=1658681004-132191-3-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=will@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®