From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Peter Zijlstra <peterz@infradead.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] objtool: Make 'sec-address' always on
Date: Wed, 21 Jun 2023 23:31:47 -0700 [thread overview]
Message-ID: <20230622063147.wpd4nxvludjjk2qa@treble> (raw)
In-Reply-To: <e7e1de1d01194df3ff4053cb0815fc2ddba33213.1687360711.git.christophe.leroy@csgroup.eu>
On Wed, Jun 21, 2023 at 05:20:31PM +0200, Christophe Leroy wrote:
> Most of the time objtool warnings are useless without the
> absolute address within the section.
>
> Today there is --sec-address option to get it printed, but
> that option is nowhere used and requires a change in Makefile
> to use it.
>
> Having the address inside the section at all time in addition
> to the address within the object doesn't hurt and will help.
>
> Remove the --sec-address option and print it at all time.
This option actually feels like clutter to me. The func+offset format
works fine, combined with scripts like objdump-func and faddr2line. And
we also have a new OBJTOOL_VERBOSE=1 option which auto-disassembles the
affected function.
On x86 we've been using func+offset for console stack traces for many
years, due to KASLR. So maybe we're just more used to it. But the
scripts make it fine.
Also it helps with identifying the same warning across different
configs/compilers.
--
Josh
next prev parent reply other threads:[~2023-06-22 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 15:20 [PATCH] objtool: Make 'sec-address' always on Christophe Leroy
2023-06-22 6:31 ` Josh Poimboeuf [this message]
2023-06-24 8:32 ` Christophe Leroy
2023-06-24 7:33 ` kernel test robot
2023-06-24 8:30 ` Christophe Leroy
2023-06-26 3:20 ` 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=20230622063147.wpd4nxvludjjk2qa@treble \
--to=jpoimboe@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=peterz@infradead.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).