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
The analysis succeeded, and I got results. However, I do see many instances of the following assertion failure in the build logs:
src/transactions/test/ManageBuyOfferTests.cpp:864:1-916:1: ERROR translating statement 'CompoundStmt'
Aborting translation of method '____C_A_T_C_H____T_E_S_T____76' in file 'src/transactions/test/ManageBuyOfferTests.cpp': "Assert_failure src/clang/cAst_utils.ml:190:53"
Aborting translation of method '____C_A_T_C_H____T_E_S_T____76' in file 'src/transactions/test/ManageBuyOfferTests.cpp'
Frontend error: "Assert_failure src/clang/cAst_utils.ml:190:53"
Backtrace:
Raised by primitive operation at file "printexc.ml" (inlined), line 259, characters 0-75
Called from file "src/backtrace.ml" (inlined), line 10, characters 2-48
I would guess (from the method name, and from what might be a reference to abstract syntax trees in the ML file name) that it's being confused by some macro trickery in the Catch-2 library.
It does appear to be having trouble finding one of the headers included by that file (and many others), but it's not obvious to me how that would be connected:
Call Stack:
------Execution Failed:
Capturing in make/cc mode...
In file included from /tmp/analyzing-1f179169b3b41698/src/transactions/test/ManageBuyOfferTests.cpp:6:
In file included from /tmp/analyzing-1f179169b3b41698/src/./ledger/LedgerTxn.h:12:
In file included from /tmp/analyzing-1f179169b3b41698/src/./ledger/LedgerHashUtils.h:7:
/tmp/analyzing-1f179169b3b41698/src/./crypto/ShortHash.h:9:10: fatal error: 'util/siphash.h' file not found
#include "util/siphash.h"
^~~~~~~~~~~~~~~~
1 error generated.
The text was updated successfully, but these errors were encountered:
With issue #4 fixed, I re-ran an analysis on the following branch:
https://github.com/rokopt/stellar-core/tree/muse-dev-experiments
The analysis succeeded, and I got results. However, I do see many instances of the following assertion failure in the build logs:
I would guess (from the method name, and from what might be a reference to abstract syntax trees in the ML file name) that it's being confused by some macro trickery in the Catch-2 library.
It does appear to be having trouble finding one of the headers included by that file (and many others), but it's not obvious to me how that would be connected:
The text was updated successfully, but these errors were encountered: