Home Dashboard Directory Help
Search

C++ Debugger Constantly Freezes by veverk


Status: 

Closed
 as External Help for as External


1
0
Sign in
to vote
Type: Bug
ID: 800832
Opened: 9/15/2013 2:44:10 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I am having problems in using Visual Studio 2012 to compile any C++ program. I am on a Windows 7 (32-bit) with latest service packs installed, and have tried everything including completely removing and reinstalling Visual Studio. But whener I run the "local windows debugger" after writing any simple program, VisuL Studio freezes. This is extremely frustrating and I am ready to give up and use a different compiler to learn C++.
Details
Sign in to post a comment.
Posted by Kuroi Kenjin on 2/5/2014 at 6:44 PM
veverk, What was your resolution? I'm trying to do DirectX programming and even with the simplest of hello world C++ programs, as soon as the program completes execution Visual Studio completely locks up, and forces an OS level lock on the intellisence DB lock file (although I thought I turned off intellisense). The laptop can't even shut down correctly due to that file lock (need to force a shut down via power button). I'm using Visual Studio 2012 and 2013 Express editions, and I'm running Windows 8.1 ( Dell XPS laptop).
Posted by Microsoft on 9/24/2013 at 7:54 PM
According to your description, we will close the issue. If you need further assistance on this or any other pre-release product issues in the future, please feel free to contact us and we will be happy to help.
Posted by veverk on 9/24/2013 at 12:48 AM
Hello, please close this request. I have now managed to get Visual Studio to compile, and am happily learning C++.

Thank you
Posted by Microsoft on 9/23/2013 at 8:15 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested. If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.
Posted by Microsoft on 9/19/2013 at 8:38 PM
Hello,

Yes, it is possible to generate dump files in that. You could get the dump file as follow steps.
1. Install and Launch VSFT.
2. Add to an existing feedback .
3. Select feedback type (crash).
4. Record a repro.
You can start recording simply by selecting a feedback type, and clicking on the “Record” button. When the dialog box appears, select the running Visual Studio instance for which you want to show the steps that cause a crash. When the crash occurs, click on the "Stop Record" button. After you do this, two files are attached to your bug report - an AutomaticCrashDump.zip file that contains information about the crash and a ReproSteps.zip file that shows the repro steps.
5.submit.
More information on how to use the tool to provide feedback is published here:https://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=26698

We look forward to hearing from you with this information.
Posted by veverk on 9/18/2013 at 12:49 PM
Apologies, I am using Visual Studio 2012 Express. Is it possible to generate dump files in that? I'm not sure how to do this, but will keep trying...
Posted by Microsoft on 9/16/2013 at 4:51 AM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a dump file so that we can conduct further research?

Visual Studio now has an extension called Microsoft Visual Studio 2012 Feedback Tool, available on the VS gallery(<http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72>).

The extension allows you to
1. upload files
2. collect trace and dump files
3. collect steps while you're repro'ing the issue
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 9/15/2013 at 2:53 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.