Injection failure in Visual Studio

[GoogleCodeExporter]

OS version: Win8.1 x64
ConEmu version: 141221

Every time I try to debug console application in Visual Studio 2013 I get 
conemu error window:

Messagebox title: ConEmuC, PID=2068
Messagebox contents:
ConEmuC.X, PID=2068
Injecting remote into PID=5176
FAILED, code=-112:0x00000006

PID 2068 is ConEmuC process
PID 5176 is my console application process

This doesn't happen when I launch my application without debugging.

*Steps to reproduction*
1. Add devenv.exe to the list of hooked executables
2. Launch debugging of console application
3. Observe conemu error

Original issue reported on code.google.com by kfa...@gmail.com on 24 Dec 2014 at 10:29

[GoogleCodeExporter]

Can you attach MiniDump's of these processes?
PID 2068 is ConEmuC process
PID 5176 is my console application process

Full dumps are not required, size will be small

Original comment by ConEmu.Maximus5 on 24 Dec 2014 at 11:14

[GoogleCodeExporter]

There is something I noticed just now - the process ConEmuC is unable to attach 
to is actually a vshost process. I don't know how to create minidump of it. The 
process explorer just creates 0 bytes file. ConEmuC minidump is attached.

Let me know if you need more info.

Original comment by kfa...@gmail.com on 24 Dec 2014 at 11:38

Attachments:

• ConEmuC.dmp

[GoogleCodeExporter]

Vshost is your debugging application. Never mind I can reproduce that now.

Original comment by ConEmu.Maximus5 on 24 Dec 2014 at 11:46

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I suspect that VS is at certain points launching executables and then attaching 
them to it's own tabs(like the powershell console as an example). I know that 
this wasn't happening before maybe 2-3-4 weeks ago, but you guys update so 
often I have no idea which version it started at :p

If you need anything from me to help fix this just let me know.

Original comment by its.the....@gmail.com on 24 Dec 2014 at 9:49