Windows error 0x8013132E, -2146233554

Detailed Error Information

CORDBG_E_DEBUGGER_ALREADY_ATTACHED[1]

Message"This process has already been attached."
Comment This process has already been attached to

HRESULT analysis[2]

FlagsSeverityFailure
Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode19 (0x013)
NameFACILITY_URT[2][3]
DescriptionThe source of the error code is .NET CLR.[2][3]
Error Code4910 (0x132e)

Questions

1vote
0answers

Visual Studio Code attach to process for debugging .NET Framework

I have this idea to use Visual Studio Code as a debugger of a working .NET Framework application. Let's assume that there is a running process that runs a full .NET Framework 64-bit application. I have all the PDBs. Would it be possible to attach to that process Visual Studio [...] read more
c#
.net
debugging
visual-studio-code
1vote
0answers

COMException: This process has already been attached. (Exception from HRESULT: 0x8013132E)

I'm using MdbgProcess and MdbgEngine to write information to an XML file like the application version, process id, time, threads, etc. I have the following code: MDbgProcess mdbgProcess = null; try { MDbgEngine debugger = new MDbgEngine(); debugger.Options.StopOnExceptionEnhanced = true; mdbgProcess = debugger.Attach(info.ProcessID); mdbgProcess.Go().WaitOne(); } catch(Exception e) { } But [...] read more
c#
debugging

Comments

Leave a comment

(plain text only)

Sources

  1. https://github.com/dotnet/coreclr/blob/v1.1.0/src/inc/corerror.xml
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0