Hi Michael,
This really helps a lot! Thank you for your information.
Thanks,
Fengjun
Michael Thayer 写道:
> Hello Fengjun,
>
> Debug versions of VirtualBox create a debug log in addition to the
> release log. The debug log is usually created in the current directory.
> However, by default nothin
Hello Fengjun,
Debug versions of VirtualBox create a debug log in addition to the
release log. The debug log is usually created in the current directory.
However, by default nothing goes into it - you need to enable the
logging you need by setting environment variables. Take a look at the
docum
Hi Brandt,
I ran SUPUninstall.exe and SUPInstall.exe and re-register the COM
component from the debug dir and still no luck.
Thank you for your kind attention.
Eric
S. Brandt 写道:
> Fengjun Eric Tian <[EMAIL PROTECTED]> writes:
>
>
>> Hi,
>>
>> I'm building 2.0.2-OSE under windows xp sp2 host
Fengjun Eric Tian <[EMAIL PROTECTED]> writes:
>
> Hi,
>
> I'm building 2.0.2-OSE under windows xp sp2 host.
> I can build a debug version using "kmk BUILD_TYPE=debug" and it is
> working, the question is, it doesn't print any debug message to the log
> file, and the first line of log file shows
Hi,
I'm building 2.0.2-OSE under windows xp sp2 host.
I can build a debug version using "kmk BUILD_TYPE=debug" and it is
working, the question is, it doesn't print any debug message to the log
file, and the first line of log file shows it's still a *release* version:
"00:00:01.347 VirtualBox 2.0.2
