FreeTrade

Thanks for the help, here's that info ``` Get flags 0 Allocate cache Program received signal SIGSEGV, Segmentation fault. 0x0000555555a81a37 in randomx::generateSuperscalar(randomx::SuperscalarProgram&, randomx::Blake2Generator&) () (gdb) bt #0 0x0000555555a81a37 in randomx::generateSuperscalar(randomx::SuperscalarProgram&,...

1. Ok. ``` [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Get flags 0 Allocate cache Program received signal SIGSEGV, Segmentation fault. 0x0000555555a9e7b0 in randomx::SuperscalarInstructionInfo::getType (this=0x0) at /root/RandomX/src/superscalar.cpp:172...

>You'll have to edit CMakeLists.txt and add add_definitions(-DTRACE) somewhere near the top and rebuild librandomx.a. Did this but doesn't seem to have made any difference to the output. Sorry, I'm...

Compiling using gcc api-example1.c -L/root/RandomX/build -lrandomx -lstdc++ -lm -lc succeeds and program runs correctly. Also the benchmark and tests run correctly. gcc -v ``` root@bchx:~/RandomX# gcc -v Using built-in specs....

OK, Thanks for the debugging help and the suggestion. Unfortunately --whole-archive hasn't made any difference :(

@sickpig - any idea why calling randomx in the context of a bitcoin-unlimited makefile build would cause a segfault? Any options I could tweak to avoid it?

Just an update - tried with a clean Ubuntu 20.04 install - same error. Adding a small $50 bounty for a fix, or suggestion that leads to a fix.

> > @sickpig - any idea why calling randomx in the context of a bitcoin-unlimited makefile build would cause a segfault? Any options I could tweak to avoid it? >...

@avrdan, thanks, yes the code runs if compiled standalone - the challenge seems to be getting it to run in the context of a Bitcoin Unlimited build.

Yes, thanks, I'm going to make a repo with my changes so it is clearer what the problem is.