Changes between Initial Version and Version 5 of Ticket #14


Ignore:
Timestamp:
Aug 27, 2015, 12:32:01 AM (9 years ago)
Author:
Valery V. Sedletski
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #14

    • Property Owner set to Valery V. Sedletski
    • Property Status new → assigned
    • Property Component Common Tasks → Driver
    • Property Milestone → VBox driver
    • Property Priority minor → major
    • Property Summary The XPCOM server traps in libc → The VBox 'Main' server traps in libc

  • Ticket #14 – Description

    initial v5  
    1 The problem is with XPCOM server (VBoxSVC.exe), like another problem with ticket #13, but if I start VBoxXPCOMIPCD.exe manually, then VBoxSVC.exe starts successfully. But if I then try to start a frontend, or a tstVBoxAPIXPCOM.exe testcase (to test if the VBox XPCOM API is working), the VBoxSVC.exe traps in libc066.dll:
     1The problem is with VBox XPCOM API server (VBoxSVC.exe, aka 'Main'), it is related to another problem in ticket #13, but after  I started VBoxXPCOMIPCD.exe manually, then VBoxSVC.exe, and if then start a frontend, or a tstVBoxAPIXPCOM.exe testcase (to test if the VBox XPCOM API is working), the VBoxSVC.exe traps in libc066.dll:
    22
    33{{{
    … …  
    2020Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.
    2121}}}
     22
     23And after this trap, VBoxXPCOMIPCD.exe terminates.