You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apart from issue #17, HDWallet tests are causing a memory violation crash. Use the command ./src/test/test_ghost --run_test=*wallet*/* to reproduce the problem. Due to #17, you can't run the relevant test in an isolated manner.
The crash is happening in: src/validation.cpp:442.
In this line: mempool.removeForReorg(&::ChainstateActive().CoinsTip(), ::ChainActive().Tip()->nHeight + 1, STANDARD_LOCKTIME_VERIFY_FLAGS);
The test new_ext_key has the problem. The issue is that ::ChainActive().Tip() is returning null. This is because there are no blocks generated in the test.
Requirement: The tests should run without errors and in both undefined behavior sanitizer and address sanitizer.
The text was updated successfully, but these errors were encountered:
TheQuantumPhysicist
changed the title
A crash happens when running tests
A crash happens when running HDWallet tests
May 26, 2020
Apart from issue #17, HDWallet tests are causing a memory violation crash. Use the command
./src/test/test_ghost --run_test=*wallet*/*
to reproduce the problem. Due to #17, you can't run the relevant test in an isolated manner.The crash is happening in:
src/validation.cpp:442
.In this line:
mempool.removeForReorg(&::ChainstateActive().CoinsTip(), ::ChainActive().Tip()->nHeight + 1, STANDARD_LOCKTIME_VERIFY_FLAGS);
The test
new_ext_key
has the problem. The issue is that::ChainActive().Tip()
is returning null. This is because there are no blocks generated in the test.Requirement: The tests should run without errors and in both undefined behavior sanitizer and address sanitizer.
The text was updated successfully, but these errors were encountered: