Custom Query (16363 matches)
Results (2479 - 2481 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10632 | fixed | a lot of App crashes under Windows 8 Release Preview | ||
| Description |
I've install the Windows 8 RP (Build 8400) in VB 4.1.16, installed the guest additions, but it unusable. Al lot of apps crash (IE, Explorer, ADK setup, VS2012 setup) WARNING: Stack unwind information not available. Following frames may be wrong. wined3dwddm_x86!WineDirect3DCreateClipper wined3dwddm_x86!WineDirect3DCreateClipper wined3dwddm_x86!WineDirect3DCreateClipper VBoxD3D9wddm_x86!VBoxWineExD3DRc9SetShRcState VBoxDispD3D_x86!VBoxDispCrHgsmiQueryClient d3d9 d3d9 d3d9 d3d9 d3d9 d3d9 d3d9 d3d9!DebugSetMute wpfgfx_v0400!CHwPipelineShader::~CHwPipelineShader wpfgfx_v0400!CMILRefCountBase::Release wpfgfx_v0400!CHwShaderCacheNode::~CHwShaderCacheNode wpfgfx_v0400!CMILRefCountBase::Release wpfgfx_v0400!CHwSurfaceRenderTargetSharedData::~CHwSurfaceRenderTargetSharedData wpfgfx_v0400!CD3DDeviceManager::UnusedNotification wpfgfx_v0400!CMILPoolResource::Release wpfgfx_v0400!CHwSurfaceRenderTarget::~CHwSurfaceRenderTarget wpfgfx_v0400!CMILCOMBase::InternalRelease wpfgfx_v0400!CMetaRenderTarget::~CMetaRenderTarget wpfgfx_v0400!CMILCOMBase::InternalRelease wpfgfx_v0400!CDrawingContext::Uninitialize wpfgfx_v0400!CMILCOMBase::InternalRelease wpfgfx_v0400!CRenderTarget::ReleaseDrawingContext wpfgfx_v0400!CSlaveHWndRenderTarget::Present wpfgfx_v0400!CComposition::Present wpfgfx_v0400!CPartitionThread::PresentPartition wpfgfx_v0400!CPartitionThread::Run wpfgfx_v0400!CPartitionThread::ThreadMain kernel32!BaseThreadInitThunk ntdll!__RtlUserThreadStart ntdll!_RtlUserThreadStart |
|||
| #5336 | duplicate | a critical error has occurred while running the virtual machine... | ||
| Description |
when virtual machine started, an error happend: a critical error has occurred while running the virtual machine and then machine execution has been stoped. |
|||
| #3284 | fixed | _init() driver entry point in vboxdrv kernel module returns bogus error value => Fixed in SVN | ||
| Description |
In this forum thread http://forums.virtualbox.org/viewtopic.php?t=13950 we found out that failures during an attempt to load the Solaris vboxdrv kernel module result in bogus error messages, like this: bash-3.2# modload -p drv/vboxdrv can't load module: Unknown error I can reproduce this issue by deliberately messing with the /etc/name_to_major file, changing vboxdrv 297 vboxflt 298 to xvboxdrv 297 xvboxflt 298 (added 'x' in front of the module names), followed by a reboot. After that change, modload -p drv/vboxdrv returns an error with errno == -1 (an unknown error code). The bug is in src/VBox/HostDrivers/Support/solaris/SUPDrv-solaris.c in function _init(). An _init(9e) function is supposed to return a positive error code from <sys/errno.h>, not -1: 192 /**
193 * Kernel entry points
194 */
195 int _init(void)
196 {
197 LogFlow((DEVICE_NAME ":_init\n"));
198
...
254
255 return -1; <<<<<<<
256 }
In my test case, the mod_install() call inside vboxdrv's _init() function failed with errrno == ENXIO; in this case ENXIO is the expected return code for the _init() function - and not -1. |
|||

