Custom Query (45 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 45)

2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#14 fixed The VBox 'Main' server traps in libc Valery V. Sedletski Valery V. Sedletski
Description

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:

[l:\src\vbox\out\os2.x86\release\bin]VBoxSVC
***************************************************
Oracle VM VirtualBox XPCOM Server Version 5.0.0_OSE
(C) 2004-2015 Oracle Corporation
All rights reserved.

Starting event loop....
[press Ctrl-C to quit]

Killed by SIGSEGV
pid=0x5d0f ppid=0x5d03 tid=0x0003 slot=0x00c8 pri=0x0200 mc=0x0001 ps=0x0010
L:\SRC\VBOX\OUT\OS2.X86\RELEASE\BIN\VBOXSVC.EXE
LIBC066 0:0004ddea
cs:eip=005b:1df4ddea      ss:esp=0053:02b9e44c      ebp=02b9e574
 ds=0053      es=0053      fs=150b      gs=0000     efl=00010212
eax=00000004 ebx=00748dac ecx=0000002d edx=00000004 edi=ffffffff esi=00000004
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

And after this trap, VBoxXPCOMIPCD.exe terminates.

#13 fixed The VBox 'Main' server app. won't start with NS_ERROR_FACTORY_NOT_REGISTERED Valery V. Sedletski Valery V. Sedletski
Description

When trying to start the VBox 'Main' server (VBoxSVC.exe), the VBoxXPCOMIPCD.exe (the XPCOM IPC daemon) won't spawn, an error from this ticket title is returned. But if I start VBoxXPCOMIPCD.exe daemon manually, then it starts successfully. But if I then try starting an appilcation, using the VBox XPCOM API (a user interface app, or a tstVBoxAPIXPCOM.exe testcase), then the next error in ticket #14 occurs.

#12 fixed cfg.sh problems klipp rklipp
Description

cfg.sh has problems defining the th OS (sed problem?) Looks like OS2 won't work but os2 after screwing around got through cfg.sh but then you get "Config.kmk: 170 error saying I have to update kBuild to 2577 ot newer", but then states it found kBuild 2624

2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.