From: "Tom Turelinckx" <tom-HiypchcOusz53ZRCpReHOg@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org
Subject: bus error on sparc64 running type-preservation test
Date: Mon, 13 Apr 2020 18:09:41 +0200 [thread overview]
Message-ID: <001f01d611ad$f1f44420$d5dccc60$@turelinckx.be> (raw)
Hi,
Since v1.4.7 DTC FTBFS on Debian sparc64 because of a bus error when running the type-preservation.dts test.
Build logs are available here:
https://buildd.debian.org/status/logs.php?pkg=device-tree-compiler&arch=sparc64
It may be an alignment issue introduced in this commit:
https://github.com/dgibson/dtc/commit/32b9c61307629ac76c6ac0bead6f926d579b3d2c
I have no idea how to fix this, but the following gdb backtrace (from v1.6.0) may help someone else:
Reading symbols from dtc...
(gdb) r -I dts -O dts -o tests/type-preservation.dts.test.dts tests/type-preservation.dts
Starting program: /build/device-tree-compiler-1.6.0/dtc -I dts -O dts -o tests/type-preservation.dts.test.dts tests/type-preservation.dts
Program received signal SIGBUS, Bus error.
0x0000010000010600 in write_propval_int (f=0x10000120300, p=0x100001268af "", len=<optimized out>, width=4)
at treesource.c:108
108 switch (width) {
(gdb) bt
#0 0x0000010000010600 in write_propval_int (f=0x10000120300, p=0x100001268af "", len=<optimized out>, width=4)
at treesource.c:108
#1 0x0000010000010c6c in write_propval (prop=0x100001268e0, f=0x10000120300) at treesource.c:251
#2 write_tree_source_node (f=0x10000120300, tree=0x10000126960, level=<optimized out>) at treesource.c:310
#3 0x0000010000010c10 in write_tree_source_node (f=0x10000120300, tree=0x10000126a50, level=<optimized out>)
at treesource.c:314
#4 0x0000010000010c10 in write_tree_source_node (f=0x10000120300, tree=0x10000126b40, level=<optimized out>)
at treesource.c:314
#5 0x0000010000010c10 in write_tree_source_node (f=0x10000120300, tree=0x10000126c30, level=<optimized out>)
at treesource.c:314
#6 0x00000100000054f4 in main (argc=<optimized out>, argv=<optimized out>) at dtc.c:351
If somebody has a suggestion for a patch, I can test it on Debian sparc64. I'm not subscribed to this list.
Best regards,
Tom Turelinckx
next reply other threads:[~2020-04-13 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 16:09 Tom Turelinckx [this message]
2020-04-13 16:29 ` bus error on sparc64 running type-preservation test Tom Turelinckx
2020-04-14 6:25 ` David Gibson
[not found] ` <20200414062534.GL48061-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2020-04-14 16:34 ` Tom Turelinckx
[not found] ` <4c0be4b4-7f6e-4612-af7b-dfffb400597a-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2020-04-21 3:22 ` David Gibson
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='001f01d611ad$f1f44420$d5dccc60$@turelinckx.be' \
--to=tom-hiypchcousz53zrcprehog@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).