[vbox-dev] How to Accumulate more information for VBox/VM debugging?

[Adam Pridgen]

Hello,

I am trying to debug the following assertion failure:

(From the VBox Headless log file)

!!Assertion Failed!!
Expression: <NULL>
Location  : /home/user/vbox/src/VBox/VMM/VMMAll/PGMAllBth.h(1462) void
pgmR3BthPAEPAESyncPageWorkerTrackDeref(PVMCPU, PPGMPOOLPAGE, RTHCPHYS,
uint16_t, RTGCPHYS)
HCPhys=0000000062e85000 wasn't found!

I am trying to identify why the Physical memory can not be found in the
Host Context.

Is it possible to capture a backtrace when an assertion occurs or log any
additional information so that I can debug the problem more effectively?

Is the VBox Debugger functional and should I try to use that for additional
information?

Right now, I am only using the output from the debugging logs as a means of
diagnosing the issue with the following flags:

VBOX_LOG="all"
VBOX_LOG_FLAGS="enabled"
VBOX_LOG_DEST="stderr"
VBOX_WITH_R0_LOGGING=1


Any debugging or analysis tips are greatly appreciated.  Thanks in advance
for your help.

-- Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.virtualbox.org/pipermail/vbox-dev/attachments/20121119/04eaf650/attachment-0002.html