Gtest executable doesn't shut down properly sometimes when debugging

[GoogleCodeExporter]

When debugging the gtest based tests with VS2008, I very often find that 
the gtest executable doesn't shut down properly.

I cannot use task manager (or any other task kill application) to shut it 
down, since I could not see the process instance in the task manager. 
while I could see the gtest output window.

I tried using Spy++ to find the PID, but that didn't help much
At least Spy++ could see the process. it looks like the process got half-
closed, so the PID wasn't really corresponding to any real process.

There is not obvious step to reproduce the issue, I think might be you 
guys could ever see or solve the issue before.

Thanks

Original issue reported on code.google.com by clarkl...@gmail.com on 26 May 2010 at 1:43

[GoogleCodeExporter]

It's unclear from your description what is going on. Do tools like Process 
Monitor or 
an attached debugger report process exiting? If not, please break into a 
hanging 
process (debug build) with a debugger, collect a stack trace, and post it here.

Original comment by vladlosev on 1 Jun 2010 at 11:51

• Changed state: Accepted

[GoogleCodeExporter]

Closed for lack of user response.

Original comment by w...@google.com on 28 Jul 2010 at 7:03

• Changed state: WontFix
• Added labels: Priority-Low
• Removed labels: Priority-Medium