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

[Mihai Hanor]

Hi Samuel,

The VirtualBox debug build is not for regular usage. The debug build runs
unoptimized code and some of its code paths may differ from a release
build. This includes debug assertions, that will stop your VM or even the
host OS without warning, if they trigger. On Windows, at least, an assert
in the VirtualBox kernel driver will stop your OS with a BSOD -- I don't
know how the Linux kernel handles a kernel module fault. With a debug
build, it may even be harder or impossible to reproduce a scenario. You can
use the official build to see where it crashes, then use a self-build
release build to obtain a detailed stack trace, if the crash is in
VirtualBox code. From this point forward, it depends on the issue and your
skills.

Best regards,
Mihai

On Tue, Apr 10, 2018 at 6:31 PM, Samuel Rats <srats at genymobile.com> wrote:

> Hi VBox people!
>
> In order to investigate an issue I recently opened
> (https://www.virtualbox.org/ticket/17644), I was looking for some
> official debug builds of the VirtualBox package, but couldn't manage
> to find any.
> Even the "testing" builds are release build.
>
> Can I find them somewhere, or should I build VirtualBox in debug mode
> myself?
> Additional question, do you know if the debug build is of VirtualBox
> is much slower than a release build, or is it still usable for
> days-to-days operations?
>
> This issue is really bothering us, and I have time to investigate/fix it.
> Thanks in advance.
>
> --
> Samuel Rats
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20180410/735c3db7/attachment.html>