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

[valdis.kletnieks at vt.edu]

On Tue, 10 Apr 2018 23:35:12 +0300, Mihai Hanor said:
> 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.

Are there any how-to guides for this?  (So far, my VirtualBox debugging needs
have only been "What API did the linux-next tree change *this* time and break
the kernel module build?", but it's always better to have debugging tools you
done use than lacking tools you could use. ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20180410/f0c52f3e/attachment.sig>