OK,
why does RTLogCreateExV deadlock?

vboxservice.cpp:547
        if (!StartServiceCtrlDispatcher(&g_aServiceTable[0]))
this method never returns (unless there is an error).

By added -vvv to the Service cmd line, I notice (in the debugger) that log 
messages are written - but I cannot find the destination of them ... VBox.log 
in system32 and in the service.exe dir remain empty, though the former one is 
recreated every time.
When disabling both services (timesync and vminfo), the service gives an error. 
Good.
When disabling either one of the services, the result is the same - deadlock(?) 
in StartServiceCtrlDispatcher.

The Service is not killed after 30s, so, it is clear that 
StartServiceCtrlDispatcher is called correctly, and soon enough.
No ideas left for the moment.

RTLogCreate in log.cpp is called twice ... is that a problem?

first:  
VBoxService.exe!RTLogDefaultInit()  Line 385 + 0x26 bytes               
VBoxService.exe!RTLogDefaultInstance()  Line 1463 + 0x5 bytes   C++
VBoxService.exe!rtR3Init(bool fInitSUPLib=false, const char * 
pszProgramPath=0x00000000)  Line 338 + 0x12 bytes C++
VBoxService.exe!RTR3Init()  Line 346 + 0x9 bytes        C++
VBoxService.exe!main(int argc=1, char * * argv=0x00372ce0)  Line 367    C++

second:
VBoxService.exe!vbglR3Init(const char * pszDeviceName=0x004c7f10)  Line 244 + 
0x26 bytes        C++
VBoxService.exe!VbglR3Init()  Line 259 + 0xa bytes      C++
VBoxService.exe!main(int argc=1, char * * argv=0x00372ce0)  Line 524 + 0x5 
bytes        C++


Yours,
Sebastian


_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-dev

Reply via email to