I have VS2010 Premium RTM version on Windows 7 Ultimate x64.
In the documentation they refer to the Memory 1-4 windows, supposedly under Debug->Windows->Memory.
I have "Enable address-level debugging" enabled in VS (Options->Debugging).
The problem is that I have no Memory menu item under Debug->Windows during debug of a c++ program.
Under Debug->Windows I have only:
Breakpoints
Parallel Tasks
Parallel Stacks
Watch ->
Locals
Call Stack
Threads
Have anyone else experienced this (and hopefully solved it)?
During the first run of VS after installation it asks you which "mode" it should run in, depending on your selection it shows or hides various menu items etc. Maybe you selected an option that hid those windows? This is described at this page.
I think you can use the information on this page to change those settings.
You might also be able to just run Devenv /ResetSettings to reset them, but not sure exactly what you'd end up with then...
Go to command Window and type in memory. It will show the Memory 1 watch window. I had to do that because I still can't find the debug command for it under customize even.
You can switch to expert mode by checking :
Tools > Settings > Expert Settings
Now you can show up Registers Window and much more other windows
The Memory window is available only if address-level debugging is enabled in the Options dialog box, Debugging node. The Memory window is not available for Script or SQL, which are languages that do not recognize the concept of memory.
or go here for other details:
http://msdn.microsoft.com/en-us/library/s3aw423e.aspx
Related
So I just installed Pop OS to my system, but notice, that neither of JetBrains apps has a top toolbar. Firstly, it's just a dark line, but after some time it just disappears.
Tried to install the software in a different ways, but got the same results. I cannot move the window, exit or minimize (since there is no options, of course), only resize it. Any ideas?
If anyone is wondering, the problem was, that "Show Window Titles" was disabled by default for me. You can turn it on on Extensions -> Pop Shell -> Show Window Titles.
90% of the apps are displaying correctly sharp and clear as it's supposed to be on my uhd laptop screen. My scaling is 150% (as default also) (because of uhd screen in 15.6" laptop, 100% is too inefficient for my eyes.)
But dev c++ and some old softwares are looking blurry.
blurry dev c++
there is a fix on windows 10 settings named "advanced scaling" that is already enabled. is there any way to fix blurry dev c++ or do you recommend better up to date ide for c++ with compiler?
advanced scaling settings windows 10
(eclipse-cpp with mingw is slow,
clion is super but uses visual c++ compiler (i dont know if is there any setting for compiler,
microsoft visual c++ is good but showing some errors for nothing, actually says "no errors" than doesnt compiles for some time)
Right click on the Dev c++
Select “Properties” from the popup menu.
Click on “Compatibility” tab.
making the settings to manually fix fuzzy text in windows 10
Select “Override high DPI scaling behavior.
Select “System (Advanced)” not "System" or "Application" from the options provided in “Scaling performed by” section.
Click on “Apply” button and then on “OK.”
Fixed screenshot
There is a new version of Dev C++ compiled with the latest version of Delphi which supports high-DPI, Unicode, and Windows 10.
https://github.com/Embarcadero/Dev-Cpp/releases
With VS2013 Pro I am not able to use "Edit and Continue" when debugging an MFC program. I created a new MFC project to test.
OS is Windows 7 64-bit and I'm running Visual Studio 2013 12.0.30110.00 Update1.
Under Tools->Options->Debugging->Edit and Continue I have Enable Edit and Continue checked. I have unchecked it and checked it, but whenever I modify the code while debugging I get the following message:
The source file has changed. It no longer matches the version of the file used to build the application being debugged.
Basically I haven't changed any settings except for the tab sizes and I've set the keyboard mapping scheme to VC6.
What setting am I missing to enable edit and continue?
Edit and Continue is disabled for native code by default. To enable:
On the Tools menu, click Options.
In the Options dialog box, open the Debugging node, and select the Edit and Continue category.
In the Native-only options group, select Enable native Edit and Continue
Edit:
Steps to test native Edit and Continue is working:
Start VS 2013
Create a new MFC project:
FILE->New Project->MFC Application->OK.
Select Finish on the MFC Application Wizard.
Build and start debugging:
BUILD->Build Solution
DEBUG->Start Debugging
Break into the program:
DEBUG->Break all
Make a code change:
Open OutputWnd.cpp and find COutputWnd::OnSize (Line 80)
Insert this line at the start of the function: cx = cx / 2;
Continue execution:
DEBUG->Continue
Resize the application window to see the effect of the code change on the Output pane at the bottom. Its width should be half the required size.
Edit and continue is also a Setting for each project.
It must be set in the compiler options under C++ -> General -> Debug Information Format: "Program Database for Edit And Continue (/ZI)"
Also the linker settings must be changed. The linker has to use incremental linking. Linker -> General -> Enable Incremental Linking = Yes or (for VC 2012 users) C++ -> All Options -> Enable Function-Level Linking = Yes (/Gy)
For more information read the MSDN.
The last hint helped, but we had to
set "Image Has Safe exception handlers" = NO(/SAFESEH:NO)
in all projects of our solution!
I did all steps described above, but nothing helps (thanks all for it).
My solution was:
Project -> Properties -> Linker -> Advanced:
set
"Image Has Safe exception handlers" = NO(/SAFESEH:NO)
Apply, Ok, and Rebuild project.
Hope it helps.
For what it's worth I've been pulling my hair out on this one as well. I finally got edit and continue working by changing the following setting:
Project > Properties > Linker > All Options > "image has safe exception handlers".
It was set to No (/SAFESEH:NO). I went in and deleted it. I didn't set it to YES, or NO. I simply kept it blank. I would love to know what it means to be blank. But edit and continue is now working for me. Maybe it will help for you.
A project with a "Release Configuration" will disable Edit and Continue.
To change this
Open "Configuration Manager"
Change Configuration for the project from Release to Debug
Rebuild and debug project
Edit and Continue will also not work if your project's Platform Toolset is set to Visual Studio 2012 (v110), instead of the usual Visual Studio 2013 (v120).
This setting is in Project > Configuration Properties > General > Platform Toolset.
The solution of this problem is on the Microsoft Documentation...
If IntelliTrace is enabled and you collect both IntelliTrace events and call information, Edit and Continue is disabled.
On Visual studios' menu go on Tools>>options - Select "IntelliTrace" tab and let IntelliTrace events only checked.. Save, restart the visual studio and.......
Your Edit and Continue will work again!
When working with Visual Studio Extensions and debugging using the experimental instance, is it possible to have the experimental instance automatically load a solution?
I did not see options, but may have been looking in the wrong place
Just right click on your project in Solution Explorer and hit properties. Debug tab. You'll see "command line arguments" as a box, which should contain "/rootsuffix Exp". These arguments are what are used to launch devenv.exe (the Visual Studio process). If you just add the full path to your solution after what is already there (quote if necessary), that should work just fine. It's really no different than doing devenv.exe from the command line.
Does anyone know what the problem here? There is no Thread Window in Debug menu.
I am using full VS2010 (Ultimate SP1).
The Threads window option only becomes available while actually Debugging a process.
Choose "Start Debugging", then go back to the same menu, and Threads (as well as many other options) will appear.
You need to be debugging in order to have the option show up in the menu:
I marked a thread as a duplicate of this one but the author was also looking for the Tasks window. Adding this answer to be clear that it is under the same menu option in newer versions of Visual Studio.
As per the answer, you need to be in debug mode for this option to show up.