Closed unisqu closed 7 years ago
Hi, we give me very few information... In general to help me diagnose any problem, please configure ULib with debug (--enable-debug), install it (make install), run any program in an environment with the DEBUG vars set to semething like: export UTRACE='0 30M -1' export UTRACE_SIGNAL='0 30M -1' (for the eventually forked instance of the program...) so it produce a trace file in its current directory for every instance of the program..
You can send me these files (compressed)
ULib definitely runs and works on Ubuntu.
What A/B test are you doing?
If you provide us with the output of your terminal, or explicit detail of what’s going wrong... we can have some insight, otherwise it’s impossible to speculate lol.
I've ran Ubuntu 16.04 and ULib seems to have Segmentation fault when I did ab test on it