Problem reports for v...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for emulat...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 244962] emulators/virtualbox-ose-additions mount -t vboxsf Operation not supported by device

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244962 mikhail.rok...@gmail.com changed: What|Removed |Added Severity|Affects Only Me |Affects Many People --

[Bug 244962] emulators/virtualbox-ose-additions mount -t vboxsf Operation not supported by device

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244962 --- Comment #5 from mikhail.rok...@gmail.com --- Link to VB bugtracker: https://www.virtualbox.org/ticket/19420 -- You are receiving this mail because: You are the assignee for the bug. ___ freeb

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 Eric W. Sattler changed: What|Removed |Added CC||reltta...@gmail.com --- Comment

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 --- Comment #22 from Jason W. Bacon --- I see... I can reproduce that problem here. Thanks for clarifying. -- You are receiving this mail because: You are on the CC list for the bug. ___ freeb

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 --- Comment #21 from Kyle Evans --- (In reply to Kyle Evans from comment #20) Sorry- and using newer GCC works around the fact that LLVM7 can no longer compile against -CURRENT headers. -- You are receiving this mail because: You are on

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 --- Comment #20 from Kyle Evans --- (In reply to Jason W. Bacon from comment #19) LLVM 8 and higher miscompile it due to either a bug in their tail-call optimization or VirtualBox doing something funky, and one can no longer create new VMs

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 --- Comment #19 from Jason W. Bacon --- What exactly is the issue that USE_GCC is working around? It's not clear from PR 244603. I just commented out USE_GCC and the VirtualBox GUI seems to work fine on 12.1-RELEASE. It also does not dep

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 --- Comment #18 from Jason W. Bacon --- How hard would it be to patch out the features not supported by base clang? In my experience porting scientific software to CentOS, which uses very old GCC suites, it was usually not that difficult (

[Bug 244847] emulators/virtualbox-ose: Memory fault after Revision 528258

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 --- Comment #17 from Graham Perrin --- (In reply to Jason W. Bacon from comment #16) > … still get a seg fault: … +1 VirtualBox segmentation fault, 5.2.34_2 on FreeBSD-CURRENT r359628