/usr/local/etc/rc.d/vboxservice script has no proper stop/shutdown process which causes core dumps each time the virtual guest is shut down Fix: #!/bin/sh # $FreeBSD: ports/emulators/virtualbox-ose-additions/files/vboxservice.in,v 1.3 2012/01/14 08:55:41 dougb Exp $ # PROVIDE: vboxservice # REQUIRE: DAEMON vboxguest # BEFORE: LOGIN # KEYWORD: shutdown # Define vboxservice_enable in /etc/rc.conf[.local] to enable it. # # vboxservice_enable (bool): Set to "NO" by default. # Set it to "YES" to enable VBoxService. . /etc/rc.subr name="vboxservice" rcvar=vboxservice_enable command="/usr/local/sbin/VBoxService" start_cmd="vboxservice_start" stop_cmd="vboxservice_stop" load_rc_config $name vboxservice_start() { PID=`/bin/ps -ax|/usr/bin/grep VBoxService|/usr/bin/grep -v grep|/usr/bin/awk '{print $1}'` if [ "X$PID" != "X" ]; then echo "*** VBoxService already started" exit 2 else $command ${vboxservice_flags} if [ $? -eq 0 ]; then echo "--- VBoxService started";fi fi } vboxservice_stop() { PID=`/bin/ps -ax|/usr/bin/grep VBoxService|/usr/bin/grep -v grep|/usr/bin/awk '{print $1}'` if [ "X$PID" = "X" ]; then echo "*** VBoxService not started" exit 2 else kill -2 $PID if [ $? -eq 0 ]; then echo "--- VBoxService stopped"; fi fi } run_rc_command "$1"
Responsible Changed From-To: freebsd-ports-bugs->vbox over to maintainer
One mistake: the "kill -2" should really be "kill -9". "kill -2" did occasionally work, but still sometimes lead to a core dump. After having tried other SIGNALS, "kill -9" has been consistently good in NOT producing any core dumps.
This looks like a bug in VBoxService itself. It probably somehow crashes at shutdown and does not terminate properly. Please send a backtrace of the coredump so that we can fix the actual problem. -- Bernhard Froehlich http://www.bluelife.at/
Sample core dump backtrace attached. On 11/25/12 22:40, FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `ports/173925'. > The individual assigned to look at your > report is: freebsd-ports-bugs. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=173925 > >> Category: ports >> Responsible: freebsd-ports-bugs >> Synopsis: ports/virtualbox-ose-additions-4.1.22 VBoxService shutdown without core dump >> Arrival-Date: Mon Nov 26 04:40:00 UTC 2012 > >
Recompiled VBox-ose-additions for FBSD-8.3 guest with "--build-debug" where VBoxService core dumps on reboot. Recompiled VBox-ose and VBox-ose-kmod with "--build-debug" for FBSD-8.3 host running VBox. Started Guest and rebooted without killing VboxService: core dump. However, the gdb backtrace still shows no symbols. Attached is the latest core dump backtrace and VboxService symbols (from "nm -s"). On 11/25/12 22:40, FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `ports/173925'. > The individual assigned to look at your > report is: freebsd-ports-bugs. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=173925 > >> Category: ports >> Responsible: freebsd-ports-bugs >> Synopsis: ports/virtualbox-ose-additions-4.1.22 VBoxService shutdown without core dump >> Arrival-Date: Mon Nov 26 04:40:00 UTC 2012 > >
back to pool