From: Shigeya Suzuki <shigeya@wide.ad.jp>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] v0.16.1 test_bitcoin fails on Deian 9
Date: Sat, 14 Jul 2018 22:48:59 +0900 [thread overview]
Message-ID: <1531576139.518511.1440639640.45D7AAB0@webmail.messagingengine.com> (raw)
Hi,
I observed strange result when running src/test/test_bitcoin on Debian 9.
I tested with the following platforms:
1) OS X High Sierra 10.13.6 with
./configiure --enable-debug
2) Debian 9 (with latest packages) with
./configure --enable-debug --disable-wallet --without-gui
3) Ubuntu 16.04 with:
./configure --with-debug --disable-wallet
strangely, configuration 2 cause core dump but others not:
Running 264 test cases...
unknown location(0): fatal error: in "validation_block_tests/processnewblock_signals_ordering": memory access violation at address: 0x00000000: no mapping at fault address
zsh: segmentation fault ./test_bitcoin
I guess it is due to toolchain differences.
Any thoughts?
Shigeya Suzuki
next reply other threads:[~2018-07-14 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 13:48 Shigeya Suzuki [this message]
2018-07-14 15:23 ` [bitcoin-dev] v0.16.1 test_bitcoin fails on Deian 9 Marco Falke
2018-07-14 15:35 ` Shigeya Suzuki
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=1531576139.518511.1440639640.45D7AAB0@webmail.messagingengine.com \
--to=shigeya@wide.ad.jp \
--cc=bitcoin-dev@lists.linuxfoundation.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