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
macOS v0.19.1 failing test: memory access violation at address: 0x02800000: no mapping at fault address #18776
Comments
Same on armhf: #15062 |
I'd like to work on this issue and I think the first thing I should start is to examine and understand the corresponding test. Is this a good first step to solving this issue? |
Can you run in valgrind?
|
Sure! Let me build Valgrind and then run the command. |
This is the output: ==90288== Memcheck, a memory error detector |
That doesn't look helpful. Maybe try gdb? |
I'm just setting breakpoints and then stepping through the test in order to look for the error, correct? Is there a more efficient/recommended debugging strategy? |
Ok, found the test case in question. Will be setting breakpoints here and stepping through it: https://github.com/bitcoin/bitcoin/blob/master/src/wallet/test/psbt_wallet_tests.cpp |
Having trouble running the tests now using make: Similar to this issue: #17664 , but it's not 100% clear what the resolution was. Besides reinstalling my repo, is there a solution to this? |
|
Great, that worked, thanks! |
Do you think it would be a good idea to detail using make distclean in the build directions here: https://github.com/bitcoin/bitcoin/blob/master/doc/build-osx.md |
Do you happen to use lldb: https://gist.github.com/fjahr/2cd23ad743a2ddfd4eed957274beca0f#gistcomment-3272312 |
I don't use lldb. What happens if you don't set any breakpoint and just |
And then do |
Looks like an upstream issue with bdb |
Would this affect my ability to debug using gdb? |
Not sure there's anything to follow up with here at the moment. If someone can recreate the issue with master we could revisit. |
ISSUE:
I'm noticing that 0.19.1 fails a particular test:
wallet/test/psbt_wallet_tests.cpp:17: Entering test case "psbt_updater_test"
unknown location:0: fatal error: in "psbt_wallet_tests/psbt_updater_test": memory access violation at address: 0x02800000: no mapping at fault address
wallet/test/psbt_wallet_tests.cpp:17: last checkpoint: "psbt_updater_test" fixture ctor
Test is aborted
What behavior did you expect?
make passes all the tests
What was the actual behavior (provide screenshots if the issue is GUI-related)?
How reliably can you reproduce the issue, what are the steps to do so?
$ make check
Easily reproducible
What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?
Bitcoin Core v0.19.1
I cloned the repo from the official Bitcoin project and then built it from source.
What type of machine are you observing the error on (OS/CPU and disk type)?
macOS Catalina 10.15.4
GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell?
No
Any extra information that might be useful in the debugging process. -->
This is normally the contents of a
debug.log
orconfig.log
file. Raw text or a link to a pastebin type site are preferred.$ grep PACKAGE_STRING= ./config.log
PACKAGE_STRING='Bitcoin Core 0.19.1'
$ head -n 20 ./src/fs.h or git log -1
==> ./src/fs.h <==
// Copyright (c) 2017-2018 The Bitcoin Core developers
// Distributed under the MIT software license, see the accompanying
// file COPYING or http://www.opensource.org/licenses/mit-license.php.
#ifndef BITCOIN_FS_H
#define BITCOIN_FS_H
#include <stdio.h>
#include
#if defined WIN32 && defined GLIBCXX
#include <ext/stdio_filebuf.h>
#endif
#include <boost/filesystem.hpp>
#include <boost/filesystem/fstream.hpp>
/** Filesystem operations and types */
namespace fs = boost::filesystem;
/** Bridge operations to C stdio */
head: or: No such file or directory
head: git: No such file or directory
head: log: No such file or directory
head: -1: No such file or directory
The text was updated successfully, but these errors were encountered: