devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tom Turelinckx" <tom-HiypchcOusz53ZRCpReHOg@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org
Subject: RE: bus error on sparc64 running type-preservation test
Date: Mon, 13 Apr 2020 18:29:52 +0200	[thread overview]
Message-ID: <002001d611b0$c2dd7d20$48987760$@turelinckx.be> (raw)
In-Reply-To: <001f01d611ad$f1f44420$d5dccc60$@turelinckx.be>

I wrote:

> I have no idea how to fix this, but the following gdb backtrace (from v1.6.0) may help someone else:

With -O0:

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.
0x0000010000017f2c in write_propval_int (f=0x1000012e300, p=0x100001348af "", len=4, width=4) at treesource.c:116
116                             fprintf(f, "0x%02"PRIx32, fdt32_to_cpu(*(const fdt32_t*)p));
(gdb) bt
#0  0x0000010000017f2c in write_propval_int (f=0x1000012e300, p=0x100001348af "", len=4, width=4) at treesource.c:116
#1  0x0000010000018704 in write_propval (f=0x1000012e300, prop=0x100001348e0) at treesource.c:251
#2  0x0000010000018b8c in write_tree_source_node (f=0x1000012e300, tree=0x10000134960, level=3) at treesource.c:310
#3  0x0000010000018c04 in write_tree_source_node (f=0x1000012e300, tree=0x10000134a30, level=2) at treesource.c:314
#4  0x0000010000018c04 in write_tree_source_node (f=0x1000012e300, tree=0x10000134b20, level=1) at treesource.c:314
#5  0x0000010000018c04 in write_tree_source_node (f=0x1000012e300, tree=0x10000134c10, level=0) at treesource.c:314
#6  0x0000010000018e28 in dt_to_source (f=0x1000012e300, dti=0x100001325c0) at treesource.c:344
#7  0x0000010000005f1c in main (argc=8, argv=0x7fefffff528) at dtc.c:351

Tom



  reply	other threads:[~2020-04-13 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 16:09 bus error on sparc64 running type-preservation test Tom Turelinckx
2020-04-13 16:29 ` Tom Turelinckx [this message]
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='002001d611b0$c2dd7d20$48987760$@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).