vbox-4.2.6: machine is stuck in Stopping status

2013-01-04 Thread Yuri
I just upgraded to 4.2.6 (from 4.2.4). Restarted Ubuntu64 that existed before, updated additions there, tried to shut it down and got it stuck in Stopping state. Now clicking "Close" button for this window doesn't pop the dialog box up asking if to send ACPI shutdown or just shut it down. This b

emultors/virtualbox-ose crash

2013-01-04 Thread Larry Rosenman
I've got the Port installed, driver loaded, and I've cleaned out all my .VirtualBox directories. Trying to do anythine with it garners: $ VBoxManage createvm --name testMachine --ostype FreeBSD_64 --register VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Code NS_ER

Re: Bug analyzed - how to fix it?

2013-01-04 Thread Jung-uk Kim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-04 15:19:30 -0500, Martin Laabs wrote: > Hi, > > I discovered it a bit further - solution 1 does not work - at least > not for newer libc. Correct, I believe you really need the compat shims. Because all supported linux_base-* lack Linux

Re: Bug analyzed - how to fix it?

2013-01-04 Thread Martin Laabs
Hi, I discovered it a bit further - solution 1 does not work - at least not for newer libc. However - since the problem is a libc function call - coulnd't I use some LD_PRELOAD library to write a if_nameindex function that is compatible to the freebsd linuxulator? Thank you, Martin

Re: Bug analyzed - how to fix it?

2013-01-04 Thread Jung-uk Kim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-04 12:40:18 -0500, Martin Laabs wrote: > Hi, > > I'm (hopefully) done with the bug analyses of > "http://www.freebsd.org/cgi/query-pr.cgi?pr=174933";. The bug in one > sentences: if_nameindex (resided in the libc) fails if called out > of

Bug analyzed - how to fix it?

2013-01-04 Thread Martin Laabs
Hi, I'm (hopefully) done with the bug analyses of "http://www.freebsd.org/cgi/query-pr.cgi?pr=174933";. The bug in one sentences: if_nameindex (resided in the libc) fails if called out of a linux binary. The cause is that the if_nameindex calls a function named __opensock that return a socket. Th

Re: Debugging a linux application and library in freebsd

2013-01-04 Thread Martin Laabs
Hi, On 01/04/13 15:29, Mateusz Guzik wrote: > > Afair linuxolator on amd64 does not support ptrace, therefore no gdb for > you. OK. Thank you. Does this mean in reverse that a i386 FreeBSD would support it? > However if this is still about > http://www.freebsd.org/cgi/query-pr.cgi?pr=174933 I

Re: Debugging a linux application and library in freebsd

2013-01-04 Thread Mateusz Guzik
On Fri, Jan 04, 2013 at 02:28:35PM +0100, Martin Laabs wrote: > Hi, > > I'm currently searching a bug in the linuxulator concerning a libc > function. Therefore it would be very helpful using gdb to trace the program > not only instruction for instruction but also with the source code and full > s

Debugging a linux application and library in freebsd

2013-01-04 Thread Martin Laabs
Hi, I'm currently searching a bug in the linuxulator concerning a libc function. Therefore it would be very helpful using gdb to trace the program not only instruction for instruction but also with the source code and full symbols. Building the linux binary that reproduce the bug is done in a VM r

Re: Reload linux.ko while system is running

2013-01-04 Thread Martin Laabs
Hi, On 01/04/13 00:27, Eitan Adler wrote: > On 3 January 2013 17:06, Mateusz Guzik wrote: >> This is definitely nvidia. > > Agreed. Sounds like nvidia. Kill X, kldunload nvidia, kldunload > linux. Let us know if that helped. Yes - it was nvidia. I changed the xserver to nv and prevent nvidia.