Bug #3436
closed
Unit test failure on Fedora 24 rawhide
0%
Description
unit-tests: asn.cpp:415: virtual CryptoPP::BERGeneralDecoder::~BERGeneralDecoder(): Assertion `0' failed.
Test setup error: signal: SIGABRT (application abort requested)
Buildlog: https://kojipkgs.fedoraproject.org//work/tasks/3597/12693597/build.log
Full task: http://koji.fedoraproject.org/koji/taskinfo?taskID=12693597
Updated by Junxiao Shi about 8 years ago
- Subject changed from Unit test failure trying to build ndn-cxx on Fedora 24 rawhide to Unit test failure on Fedora 24 rawhide
- Description updated (diff)
- Assignee set to susmit shannigrahi
When reporting a unit testing error, include the following:
- Execute unit testing with logging enabled:
./unit-tests -l test_suite.
When reporting a crash, include a gdb log:
gdb --args ./unit-tests -l test_suiterun- when crash occurs,
bt full
Please add the requested information.
Updated by Ashlesh Gawande over 7 years ago
Lei in our lab was cross compiling ndn-cxx, NFD for Raspberry Pi and was having this same error when he ran NFD.
(Latest version of ndn-cxx, NFD as of 11/11/16)
He simply commented out the line as suggested here:
https://github.com/monero-project/kovri/issues/210#issuecomment-227081690
(https://github.com/weidai11/cryptopp/commit/bb3276389e445117d1592d31a777070381aefa5f#diff-5e0f7463043d19c9c331a17ddd331dd7)
and now NFD runs fine.
Cryptopp version he used was 563.
Updated by Alex Afanasyev over 7 years ago
We had similar issue recently with NFD-android. The latest version of cryptopp includes the same solution of commenting out the assert.
Updated by susmit shannigrahi over 7 years ago
Alex Afanasyev wrote:
We had similar issue recently with NFD-android. The latest version of cryptopp includes the same solution of commenting out the assert.
This happens on Fedora 25 as well.
Updated by susmit shannigrahi over 7 years ago
Upstream has fixed this issue in CRYPTOPP 5.6.5. Tested and confirmed.
https://github.com/weidai11/cryptopp/releases/tag/CRYPTOPP_5_6_5
Updated by Junxiao Shi almost 7 years ago
- Status changed from New to Closed
From note-5 I understand this bug is resolved by upgrading CryptoPP. If this understanding is wrong, please reopen.