-
Notifications
You must be signed in to change notification settings - Fork 35.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tinyformat.h porting problem? #13933
Comments
Please include exact steps to reproduce. (commit, os, every command line, ...) |
Thanks @MarcoFalke for the follow-up. Actually the steps to reproduce crash are just not many. There's a core-dump right the --help command. Here below are the setup details, a run session & GDB trace as well. Can you please help figure out what's going wrong? [Platform]
[ bitcoin-core] bitcoin $ git worktree add ../v0.9.0 --no-checkout --detach && cd ../v0.9.0 && git checkout -b v0.9.0 -- Options used to compile and link: target os = linux CC = gcc Program received signal SIGABRT, Aborted.
|
can somebody help? |
Is this still an issue with a recent version of Bitcoin Core? If yes, what are the steps to reproduce? |
Hi.
From a self-compiled bitcoin core from sources, getting the following error.
$ src/bitcoind --help
bitcoind: ./tinyformat.h:515: void tinyformat::detail::FormatArg::format(std::ostream&, const char*, const char*, int) const: Assertion `m_formatImpl' failed.
Aborted (core dumped)
$
It's a NULL pointer assertion on m_formatImpl from tinyformat.h at #515. This issue is reproducible across versions, have tried all the way down to version 0.9.0 & witnessing the same assertion failure.
Using tools: TileGx, Linux (3.4.61), GCC / G++ 4.9.2, Libboost 1.64.0.
Believe, the dependency environment is prepared with correct versions ( Ref: https://github.com/bitcoin/bitcoin/blob/master/doc/dependencies.md ). The issue seems to be due to a combination of CPU (tilegx), GCC libraries. Tbh, can't get my head around when it comes to C++ code.
Can someone please help figure out the problem?
Thanks very much in advance.
Girish.
The text was updated successfully, but these errors were encountered: