You are not logged in.
Pages: 1
Although linux is our production environment I'm testing with FreeBSD perhaps as a replacement in future. My last tests some month ago were successful under Proxmox in a FreeBSD13 VM.
Now I'm testing with a real FreeBSD13 host and here I can first compile successfully my program but it comes a runtime exception after starting when mORMot2 initialize a global mutex between initialization und finalization. I've tested with fpc 3.2.0, 3.2.2 and 3.3.1.
gdb show's:
Program received signal SIGSEGV, Segmentation fault.
Address not mapped to object.
mutex_unlock_common (m=0x90139f708, cv=false, mtx_defer=0x0)
at /usr/src/lib/libthr/thread/thr_mutex.c:973
973 if (__predict_false(PMUTEX_OWNER_ID(m) != id))
Something seems to be different under FreeBSD with /lib/libthr.so.3 compared to /lib/x86_64-linux-gnu/libpthread.so.0 under Linux.
PS:
I've also tried several versions of FreeBSD13 and I've build FreeBSD 13.2 Release from source with connected Kernel.
Offline
To be honest, I just tried to compile with BSD systems.
For BSD system, we run the tests on MacOS only as part of our continuous integration.
I did not make lot of FreeBSD nor OpenBSD debug.
Any input is welcome.
Offline
Pages: 1