From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [Bug] Nullpointer Exception in of_diff
Date: Mon, 12 Jun 2023 16:50:24 +0200 [thread overview]
Message-ID: <044fee32-5560-2e85-a0d3-cc7cea71ed48@pengutronix.de> (raw)
In-Reply-To: <f4fc4921-e722-353c-c901-7af8976043e4@pengutronix.de>
Hello Johannes,
On 12.06.23 16:26, Johannes Zink wrote:
> Hi,
>
> I observed a Nullpointer Exception in barebox barebox 2023.05.0 on a Rock3a when calling
>
> of_diff . .
This should be already fixed in next. You can ask Sascha to pick
"commands: of_diff: simplify error handling" to master if that
fixes your issue.
> on the shell. Please find the complete dump below:
[snip]
> The behaviour is stable and reproducable on a Rock3A, probably also on other boards. Maybe someone of the more experienced barebox devs already has an idea what's going wrong here and wants to have a closer look, otherwise I'd probably give it a shot within the next few days (and if I manage to find some spare time...)
You can pipe barebox crash logs into Linux scripts/decode_stacktrace.sh
to get line numbers (don't forget to set ARCH/CROSS_COMPILE).
Enabling CONFIG_KASAN=y can also be very useful to pinpoint the origin
of memory corruptions.
Cheers,
Ahmad
>
> Best regards
> Johannes
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-06-12 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 14:26 Johannes Zink
2023-06-12 14:50 ` Ahmad Fatoum [this message]
2023-06-13 11:42 ` Johannes Zink
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=044fee32-5560-2e85-a0d3-cc7cea71ed48@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=j.zink@pengutronix.de \
/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