Changes between Initial Version and Version 5 of Ticket #14
- Timestamp:
- Aug 26, 2015, 10:32:01 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14
-
Property
Status
changed from
new
toassigned
-
Property
Component
changed from
Common Tasks
toDriver
-
Property
Summary
changed from
The XPCOM server traps in libc
toThe VBox 'Main' server traps in libc
-
Property
Priority
changed from
minor
tomajor
-
Property
Milestone
changed from
to
VBox driver
- Property Owner set to Valery V. Sedletski
-
Property
Status
changed from
-
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 tostart a frontend, or a tstVBoxAPIXPCOM.exe testcase (to test if the VBox XPCOM API is working), the VBoxSVC.exe traps in libc066.dll:1 The 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: 2 2 3 3 {{{ … … 20 20 Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it. 21 21 }}} 22 23 And after this trap, VBoxXPCOMIPCD.exe terminates.