Created attachment 254882 [details] VirtualBox_FBSD-CUR_02_11_2024_21_12_41 After ``service vboxguest onestart`` . vbox-additions installed via ``pkg ins ...`` and version 6.1.50 . Thank you for development & support. Joy, Happiness and Satisfaction! Resources for prosperous life!!)
Created attachment 254883 [details] VirtualBox_FBSD-CUR_02_11_2024_21_13_27
What version of FreeBSD do you use? Did you rebuild port self?
(In reply to Vladimir Druzenko from comment #2) Latest 1500026 main-n273396-d839cf2fbb47 Nov 2, 19:43 ; llvm 19.1.2 . Yes, but virtualbox-ose-additions rebuilt didn't help. If you need any extra debug info, please, point me to proper debug commands.
(In reply to mikhail.rokhin from comment #3) Can you try building it with different versions of LLVM from ports?
(In reply to Vladimir Druzenko from comment #4) Is it better to build it with GCC ?)
NB I doubt it is failure of anything, but kernel: whatsoever program fails, kernel should not panic, managing resources properly & protectively.
The panic backtrace in the attachment shows the crash is in VirtualBox's kernel code.
(In reply to Vladimir Druzenko from comment #4) GCC 13, 14 and LLVM 15, 18 both were installed via ``pkg ins ...`` and both failed to compile the port with multiple errors about undefined symbols & syntaxis errors at ld linking stage. May there be something hardcoded about compiler within the port? World's built-in LLVM 19 succeeded in compilation. Could you point me to the right substitution for USE_GCC for LLVM, smth like USE_LLVM=15 , please? As of `DEFAULT_VERSIONS+= llvm=15`` in make.conf fails and the port uses built-in LLVM 19 instead, and it's a long way to print CC= , CXX= , CPP=, etc. in ``make`` command line.
(In reply to mikhail.rokhin from comment #8) Add in port's Makefile: "USES+=llvm:N" where N=19,18,17,16,15,14.