Page 1 of 1

Visual Studio 2008 Debug - Fatal Execution Engine Error

PostPosted: 12. May 2010, 04:51
by bw2010
Hi All,

Using Visual Studio 2008 with 3.1.6 and 3.1.8 I have found the following issue (if I downgrade to 3.1.4 everything works fine):

1) Run Visual Studio 2008
2) Open a windows forms project *
3) Set a breakpoint and debug the project (ie press F5)
4) Visual Studio compiles the project and attempts to debug, however the debugger never starts.

Looking in the Visual Studio output window, the following is logged:
The program '[1080] Sample.vshost.exe: Managed' has exited with code -1073740940 (0xc0000374)

Also, in the application event log, the following is logged:
Event ID: 1023
Event Source: .NET Runtime
Event Data: .NET Runtime version 2.0.50727.4927 - Fatal Execution Engine Error (000007FEF9CDFA42) (80131506)

There is no information logged in the virtualbox machine log.

* Not all projects exhibit this issue, I have not managed to narrow down the mitigating circumstances

As I mentioned above, If I downgrade to 3.1.4, the issue goes away.

Any tips on how to troubleshoot this any further, does virtualbox have a verbose logging mode?

Should I file a bug report?

Thanks in advance.

showvminfo output below:
Code: Select all   Expand viewCollapse view
Sun VirtualBox Command Line Management Interface Version 3.1.8
(C) 2005-2010 Sun Microsystems, Inc.
All rights reserved.

Name:            BOLDEV01
Guest OS:        Windows 7 (64 bit)
UUID:            e60134de-da4c-4602-90e5-2bfc3df41a9d
Config file:     D:\Virtual Machines\Machines\BOLDEV01\BOLDEV01.xml
Hardware UUID:   e60134de-da4c-4602-90e5-2bfc3df41a9d
Memory size:     1536MB
VRAM size:       128MB
Number of CPUs:  1
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             on
Time offset:     0 ms
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging:   on
VT-x VPID:       off
State:           running (since 2010-05-12T01:28:38.042000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: on
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0):            IDE Controller
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Name (1):            Floppy Controller
Storage Controller Type (1):            I82078
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  1
Storage Controller Port Count (1):      1
IDE Controller (0, 0): D:\Virtual Machines\Hard Disks\BOLDEV01\BOLDEV01.vdi (UUID: 031f4535-3f8d-49dd-829d-a705e3706298)
IDE Controller (1, 0): C:\PROGRA~1\Sun\VIRTUA~1\VBoxGuestAdditions.iso (UUID: 357a3bd4-157c-4814-8b49-75d9b55dcae1)
Floppy Controller (0, 0): Empty
NIC 1:           MAC: 080027CE138D, Attachment: Bridged Interface 'Intel(R) 82566DC Gigabit Network Connection', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
UART 1:          disabled
UART 2:          disabled
Audio:           disabled
Clipboard Mode:  Bidirectional
Video mode:      1400x1050x32
VRDP:            disabled
USB:             enabled

USB Device Filters:


Available remote USB devices:


Currently Attached USB Devices:


Shared folders:  <none>

VRDP Connection:    not active
Clients so far:     0


Statistics update:                   disabled

Re: Visual Studio 2008 Debug - Fatal Execution Engine Error

PostPosted: 26. May 2010, 06:03
by bw2010

Still happens in 3.2.0

Any ideas?

Re: Visual Studio 2008 Debug - Fatal Execution Engine Error

PostPosted: 26. May 2010, 09:35
by bw2010
Just noticed I can workaround the issue by changing the platform target (visual studio project properties) from Any CPU to x86.

So I guess its an incompatibility between Virtualbox and .NET x64.

If I set the platform target to x64, the problem returns.

Good thing my application doesn't require 64bit support....