On 6/6/12, Aleksey Bragin aleksey@reactos.org wrote:
Hello, it's time for my periodical rant about debug log mess again. The example below is made using latest VirtualBox 3.
Suggestions and questions:
(/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/ntuser.c:161) err: Enter NtUserInitialize(0, 00000000, 00000000) (/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/display.c:79) err: InitDisplayDriver (\Device\Video0, \Registry\Machine\System\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Services\VBE\Device0);
What happens here? It's a normal bootup, everyone should see this. Why is invalid window station handle being passed, why do we need NtUserInitialize to produce ERR debug print, along with InitDisplayDriver. Are those errors? If not, then why the hell are they being printed? If yes, then I don't see any info about actual errors.
NtUserInitialize when used with Automatic Regression Tests let's know where we are at during boot. Justin Case of a lockup.
(/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/window.c:2416) err: DestroyWindow AOW AOW? ORLY?
This one just snicked in...
There is the Release Build to play with, without the debugs....