Re: [vbox-dev] VirtualBox official debug builds/debug symbols

No it doesn't from what I remember. Env variables are not available in kernel context. This means that unless on Windows you really like BSODs (or have set up kernel debugging) or on the other platforms like panics (or where applicable have set up kernel debugging) you really should go for release

Re: [vbox-dev] VirtualBox official debug builds/debug symbols

I would not be able to answer that properly without investigation. I expect that it does, but that you need to work out how to pass that variable to the driver. (In Linux a module parameter might do it. The source code will know.) Regards Michael 11.04.2018 11:17, Mihai Hanor wrote: > Hi, >

Re: [vbox-dev] VirtualBox official debug builds/debug symbols

Hi, Does VBOX_ASSERT=no affect kernel mode assertions? Regards, Mihai On Wed, Apr 11, 2018 at 11:30 AM, Michael Thayer wrote: > Hello Both, > > On the whole the debug build should be usable for day to day work for a > developer (not for an innocent person of

Re: [vbox-dev] VirtualBox official debug builds/debug symbols

Hello Both, On the whole the debug build should be usable for day to day work for a developer (not for an innocent person of course). Assertions can be made non-fatal by either running in the debugger ("gdb VBoxSVC" in one terminal and "gdb --args VirtualBox --startvm ..." in another) - the