search

TobiasChe / conemu-maximus5

Automatically exported from code.google.com/p/conemu-maximus5
0 stars 0 forks source link

Switching to Visual Studio shows "Injecting failed" message. #1658

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
OS version: Win7 x64
Visual Studio 2013 (seems to happen also on Visual Studio 2010).
ConEmu version: 140707 preview

I'm running several Visual Studio instances (most 2013, sometimes 2010) at the 
same time. Some of them are used to debug console applications, which are 
captured by ConEmu.
In addition, I have several ConEmu windows/tabs open (primarily git bash).

Switching to one of the Visual Studio windows (doesn't seem to matter if it is 
one with a console application or with a GUI application) yields the following 
message:

---------------------------
ConEmuC, PID=24452
---------------------------
ConEmuC.X, PID=24452
Injecting remote into PID=836
FAILED, code=-300:0x00000005
---------------------------
OK   
---------------------------

And that everytime I do a task switch. I'm not sure how to reproduce this, but 
it's really annoying. The PID in the message is always the PID of the Visual 
Studio instance I'm switching to.

Until yesterday, I used an older version (like 1306XX or something) which did 
not have this bug. I updated to get rid of another problem with debugging 
(captured console applications could not be debugged properly).

Original issue reported on code.google.com by Floechen...@gmx.de on 31 Jul 2014 at 8:46

GoogleCodeExporter commented 8 years ago 
Note that when working with the Visual Studio instance, the message pops up 
from time to time even though I'm staying within the window.

Original comment by Floechen...@gmx.de on 31 Jul 2014 at 9:01

GoogleCodeExporter commented 8 years ago 
Antiviral or sort of software?

Original comment by ConEmu.Maximus5 on 31 Jul 2014 at 9:08

GoogleCodeExporter commented 8 years ago 
Another question. What accounts are used for ConEmu.exe and devenv.exe?

Can you build ConEmu and do some debugging?

Original comment by ConEmu.Maximus5 on 31 Jul 2014 at 9:44

GoogleCodeExporter commented 8 years ago 
Using Microsoft Security Essentials. But I'm doing so for a long time now, i.e. 
no new antivirus. I attached my configuration to #1659. I guess this problem 
will also be gone after a restart. I'm sometimes not really nice to my programs 
and interrupt debugging when within critical functions, not sure if that may 
lead to this kind of problem.

I'm running ConEmu.exe and devenv.exe from the same account, an Administrator 
account with UAC enabled (i.e. requires elevation for admin actions). Both are 
run unelevated (don't know if that's a problem for the hook).

I could build ConEmu and debug, but I've currently not the time. The problem is 
happening on my machine at work, not at home. I'll report when I find anything 
that may be helpful.

Original comment by Floechen...@gmx.de on 31 Jul 2014 at 9:59

GoogleCodeExporter commented 8 years ago 
Just noticed. You are using OldBuild. Update to the latest one, bay be that 
will fix both your issues.

Original comment by ConEmu.Maximus5 on 31 Jul 2014 at 2:30