[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YidgcE0ypmKWzvai@qian>
Date: Tue, 8 Mar 2022 08:56:00 -0500
From: Qian Cai <quic_qiancai@...cinc.com>
To: Daniel Thompson <daniel.thompson@...aro.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] configs/debug: set CONFIG_DEBUG_INFO=y properly
On Tue, Mar 08, 2022 at 10:42:15AM +0000, Daniel Thompson wrote:
> On Tue, Mar 01, 2022 at 03:29:20PM -0500, Qian Cai wrote:
> > CONFIG_DEBUG_INFO can't be set by user directly,
>
> What do you mean by "can't be set by user directly"? DEBUG_INFO
> is fully controlable via menuconfig.
On linux-next, we no longer able to select DEBUG_INFO directly due to this
patch:
https://lore.kernel.org/all/20220125075126.891825-1-keescook@chromium.org/
Thus, this patch will work on both the mainline and linux-next.
> Does this change actually work in the kernels it has merged into?
>
> DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT existence is predicated on DEBUG_INFO
> being set. It makes no sense at all to set the former without the later.
It works fine here.
$ git reset --hard v5.17-rc7
$ rm .config
$ make ARCH=arm64 defconfig debug.config
$ grep -i debug_info .config
CONFIG_DEBUG_INFO=y
Powered by blists - more mailing lists