From: Xiaoming Ni <nixiaoming@huawei.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Cc: <dima@arista.com>, <will@kernel.org>, <jpoimboe@redhat.com>,
<akpm@linux-foundation.org>, <christian.brauner@ubuntu.com>,
<viro@zeniv.linux.org.uk>, <ldufour@linux.ibm.com>,
<amanieu@gmail.com>, <walken@google.com>,
<ben.dooks@codethink.co.uk>, <tglx@linutronix.de>,
<mingo@kernel.org>, <vincent.whitchurch@axis.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wangle6@huawei.com>,
<luohaizheng@huawei.com>
Subject: Re: [PATCH] arm:traps: Don't print stack or raw PC/LR values in backtraces
Date: Mon, 12 Oct 2020 10:23:58 +0800 [thread overview]
Message-ID: <ac712544-e479-26aa-226b-1859517ea60e@huawei.com> (raw)
In-Reply-To: <20201011213238.GN1551@shell.armlinux.org.uk>
On 2020/10/12 5:32, Russell King - ARM Linux admin wrote:
> On Fri, Oct 09, 2020 at 10:18:20AM +0200, Sebastian Andrzej Siewior wrote:
>> On 2020-10-09 09:08:50 [+0100], Russell King - ARM Linux admin wrote:
>>> I am really not happy about this - it hurts at least my ability to
>>> debug the kernel when people post oopses to the mailing list. If
>>> people wish to make the kernel harder to debug, and are prepared
>>> to be told "your kernel is undebuggable" then this patch is fine.
>>
>> I haven't look at the patch but don't they keep/add the representation:
>> PC: symbol+offset/size
>> LR: symbol+offset/size
>>
>> ? This is needed at very least as a replacement for the missing address.
>
> I don't have a problem getting rid of the hex numbers in [< >]
> although then I will need to convert the symbol back to an address
> using the vmlinux to then calculate its address to then find the
> appropriate place in the objdump output - because objdump does
> _not_ use the symbol+offset annotation. Yes, I really do look up
> the numeric addresses in the objdump output to then read the
> disassembly.
>
> $ objdump -d vmlinux | less
>
> and then search for the address is the fastest and most convenient
> way for me rather than having to deal with some random script.
>
> Maybe I'm just antequated about how I do my debugging, but this
> seems to me to be the most efficient and fastest way.
>
The loading address of the kernel module is not fixed, so symbol+offset
is more useful than a hexadecimal address when the call stack contains
kernel module symbols.
Delete the PC/LR address and retain the sysbol+offset. The kernel can
still be debugged.
Thanks
Xiaoming Ni
next prev parent reply other threads:[~2020-10-12 2:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 7:59 [PATCH] arm:traps: Don't print stack or raw PC/LR values in backtraces Xiaoming Ni
2020-10-09 8:08 ` Russell King - ARM Linux admin
2020-10-09 8:18 ` Sebastian Andrzej Siewior
2020-10-09 8:58 ` Xiaoming Ni
2020-10-11 21:32 ` Russell King - ARM Linux admin
2020-10-12 2:23 ` Xiaoming Ni [this message]
2020-10-12 10:03 ` Sebastian Andrzej Siewior
2020-10-12 11:06 ` Russell King - ARM Linux admin
2020-10-10 17:55 ` Josh Poimboeuf
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=ac712544-e479-26aa-226b-1859517ea60e@huawei.com \
--to=nixiaoming@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=amanieu@gmail.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bigeasy@linutronix.de \
--cc=christian.brauner@ubuntu.com \
--cc=dima@arista.com \
--cc=jpoimboe@redhat.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luohaizheng@huawei.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.whitchurch@axis.com \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.com \
--cc=wangle6@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).