From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [RFC PATCH] MIPS: Kconfig: Select ARCH_WANT_FRAME_POINTERS
Date: Mon, 16 Nov 2020 13:09:28 +0300 [thread overview]
Message-ID: <9b6318d8-1112-d271-b775-209ccc526fcf@gmail.com> (raw)
In-Reply-To: <aa8b9e92-8851-60d2-32d1-cec99be1af57@loongson.cn>
On 16.11.2020 12:47, Tiezhu Yang wrote:
[...]
>>> Select ARCH_WANT_FRAME_POINTERS to fix the following build error under
>>> CONFIG_DEBUG_ATOMIC_SLEEP:
>>>
>>> CC arch/mips/kernel/signal.o
>>> {standard input}: Assembler messages:
>>> {standard input}:1775: Error: Unable to parse register name $fp
>>> scripts/Makefile.build:283: recipe for target 'arch/mips/kernel/signal.o'
>>> failed
>>> make[2]: *** [arch/mips/kernel/signal.o] Error 1
>>> scripts/Makefile.build:500: recipe for target 'arch/mips/kernel' failed
>>> make[1]: *** [arch/mips/kernel] Error 2
>>> Makefile:1799: recipe for target 'arch/mips' failed
>>> make: *** [arch/mips] Error 2
>>>
>>> I think it is useful to get debugging information as described in the
>>> following texts:
>>>
>>> lib/Kconfig.debug
>>> config FRAME_POINTER
>>> bool "Compile the kernel with frame pointers"
>>> ...
>>> default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
>>> help
>>> If you say Y here the resulting kernel image will be slightly
>>> larger and slower, but it gives very useful debugging information
>>> in case of kernel bugs. (precise oopses/stacktraces/warnings)
>>>
>>> Documentation/dev-tools/kgdb.rst
>>> This option inserts code to into the compiled executable which saves
>>
>> So to or into? :-)
>
> Hi Sergei,
>
> Thanks for pointing that out，this may be a typo which should be "into".
Oops, I didn't realize it was a quote from the KGDB docs... :-)
> I will update the commit message to correct it.
Thank you!
> Thanks,
> Tiezhu
[...]
MBR, Sergei
next prev parent reply other threads:[~2020-11-16 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 5:03 [RFC PATCH] MIPS: Kconfig: Select ARCH_WANT_FRAME_POINTERS Tiezhu Yang
2020-11-16 9:08 ` Sergei Shtylyov
2020-11-16 9:47 ` Tiezhu Yang
2020-11-16 10:09 ` Sergei Shtylyov [this message]
2020-11-20 22:37 ` Maciej W. Rozycki
2020-11-21 1:32 ` Tiezhu Yang
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=9b6318d8-1112-d271-b775-209ccc526fcf@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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).