From: Elliot Berman <quic_eberman@quicinc.com>
To: Xiong Nandi <xndchn@gmail.com>
Cc: <akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<quic_bjorande@quicinc.com>, <cmllamas@google.com>
Subject: Re: [PATCH v2 2/2] scripts/decode_stacktrace.sh: better support to ARM32 module stack trace
Date: Wed, 22 May 2024 19:00:30 -0700 [thread overview]
Message-ID: <20240522185741891-0700.eberman@hu-eberman-lv.qualcomm.com> (raw)
In-Reply-To: <20240523010318.12934-3-xndchn@gmail.com>
On Thu, May 23, 2024 at 09:03:18AM +0800, Xiong Nandi wrote:
> Sometimes there is special characters around module name in stack trace,
> such as ARM32 with BACKTRACE_VERBOSE in "(%pS)" format, such as:
> [<806e4845>] (dump_stack_lvl) from [<7f806013>] (hello_init+0x13/0x1000 [test])
>
> After stripping other characters around "[module]", it can be finally decoded:
> (dump_stack_lvl) from hello_init (/foo/test.c:10) test
>
> Signed-off-by: Xiong Nandi <xndchn@gmail.com>
> ---
> scripts/decode_stacktrace.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/decode_stacktrace.sh b/scripts/decode_stacktrace.sh
> index 2bc3a54ffba5..324e4a6c260a 100755
> --- a/scripts/decode_stacktrace.sh
> +++ b/scripts/decode_stacktrace.sh
> @@ -283,8 +283,8 @@ handle_line() {
>
> if [[ ${words[$last]} =~ \[([^]]+)\] ]]; then
> module=${words[$last]}
> - module=${module#\[}
> - module=${module%\]}
> + module=${module#*\[}
> + module=${module%\]*}
I think it'd be better to just remove the parenthesis similar to how is
done in the symbol name.
That is:
module=${words[$last]}
module=${module#\[}
module=${module%\]}
# some nice comment explaining only the closing paren is
# need to be stripped
module=${module%\)}
modbuildid=${module#* }
> modbuildid=${module#* }
> module=${module% *}
> if [[ $modbuildid == $module ]]; then
> --
> 2.25.1
>
prev parent reply other threads:[~2024-05-23 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 0:56 [PATCH] " xndcn
2024-05-22 1:05 ` Xiong Nandi
2024-05-22 2:48 ` Elliot Berman
2024-05-22 4:10 ` xndcn
2024-05-23 1:03 ` [PATCH v2 0/2] scripts/decode_stacktrace.sh: better support to ARM32 Xiong Nandi
2024-05-23 1:03 ` [PATCH v2 1/2] scripts/decode_stacktrace.sh: wrap nm with UTIL_PREFIX and UTIL_SUFFIX Xiong Nandi
2024-05-23 1:56 ` Elliot Berman
2024-05-23 1:03 ` [PATCH v2 2/2] scripts/decode_stacktrace.sh: better support to ARM32 module stack trace Xiong Nandi
2024-05-23 2:00 ` Elliot Berman [this message]
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=20240522185741891-0700.eberman@hu-eberman-lv.qualcomm.com \
--to=quic_eberman@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=cmllamas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=xndchn@gmail.com \
/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®