Bug 12699 - [CorDebugger] Debugger pops up: Error HRESULT EFAIL has been returned from a call to a COM component.
Summary: [CorDebugger] Debugger pops up: Error HRESULT EFAIL has been returned from a ...
Status: RESOLVED DUPLICATE of bug 11304
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.8
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-06-14 16:19 UTC by Confused
Modified: 2013-06-14 16:47 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Confused 2013-06-14 16:19:32 UTC
Running Xamarin studio on windows 8.

In debugging an application that runs OpenGL via openTK  I occasionally get the following error:

Error HRESULT EFAIL has been returned from a call to a COM component.

System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
   at Microsoft.Samples.Debugging.CorSymbolStore.ISymUnmanagedReader.GetMethodFromDocumentPosition(ISymUnmanagedDocument document, Int32 line, Int32 column, ISymUnmanagedMethod& retVal)
   at Microsoft.Samples.Debugging.CorSymbolStore.SymReader.GetMethodFromDocumentPosition(ISymbolDocument document, Int32 line, Int32 column)
   at MonoDevelop.Debugger.Win32.CorDebuggerSession.OnInsertBreakEvent(BreakEvent be)
   at Mono.Debugging.Client.DebuggerSession.RetryEventBind(BreakEventInfo binfo)
Comment 1 Jeffrey Stedfast 2013-06-14 16:22:42 UTC
Make sure that you are building a 32bit exe. 64bit exes are not supported when using the Microsoft .NET runtime.

Your other option is to install the Mono runtime and target that for debugging.
Comment 2 Confused 2013-06-14 16:35:43 UTC

The project is already 32bit. 

Swapping to 64bit gives a slightly different error message: System.Runtime.InteropServices.COMException (0x80070032)

Additionally, the dialog seems to eventually causes weirdness if left open.

Basically, it pops under the main window and vanishes leaving the main window unusable until it is closed, which is hard to do as it is behind the main window.
Comment 3 Jeffrey Stedfast 2013-06-14 16:40:20 UTC
I would recommend that you use the Mono runtime for debugging. The Soft Debugger backend is lightyears ahead of the CorDebugger backend.
Comment 4 Confused 2013-06-14 16:47:14 UTC
Cool, will install mono and go from there. 

Thanks for the help.

*** This bug has been marked as a duplicate of bug 11304 ***