How to keep Memory View open in CLion? - clion

Whenever I open the Memory View by pressing Ctrl+Enter (or rightclick and "View in Memory") on an active variable during debugging from the watches window, it closes after I re-run the program or stop it.
I've tried pinning the tab and searching through the settings but to no avail.
Is there any way to keep it open even after I stop/re-run the debug of the code? Visual Studio allows this.

Related

Can I make Visual Studio stay where it is in the code on breakpoint hit?

When I have a code file open and a breakpoint hits, Visual Studio automatically switches the open page to the corresponding file and places the cursor on the corresponding line.
This is quite annoying in my present use case where I'm looking at-on screen values and code lines in a shader file simultaneously, using a breakpoint and F5 to jump to the next frame will switch from the shader file to my breakpoint location.
This is not about VS stealing focus, but about preserving internal focus within VS. I just want silent breakpoint hits.
In Visual Studio 2015, you need to right click the breakpoint to choose "Action" option. It will open the Breakpoint Settings dialog. Now you can add the message that you want to write in Output window and check "Continue execution" option. After setting the output message, the breakpoint will not be hit.
In Visual Studio right click on the break point. In the context menu select the When Hit... menu option. On the When Breakpoint Is Hit dialog box check the Continue execution checkbox. Use the Print a message text box to customize a message to be written to the Debug output so you can tell the breakpoint was hit.

How do I turn debugging in disassembly off permanently?

Whilst debugging a console app in c# and VS2008, disassembly window appears uninvited.
I am debugging my code line by line using F11. I have break points set and it starts off well then after a call in a method to open database connection, the debugger opens disassembly window and stays there. I have right-clicked on disassembly tab and selected hide but the window pops again as soon as I hit F11.
How do I turn debugging in disassembly off permanently?
Go to Debug->Options and Settings, uncheck the box for Enable address-level debugging and that should do what you want.
You also may want to check Enable Just My Code if it is not checked.

default debug window setting in VS 2010

I would like to have the default window during a debug session be 'Locals'.
I think there a way to do this by blowing away all other devenv settings, but I'm reluctant to do that as the latest R# seems related somehow.
How can I make the Locals window be the default while debugging?
Berryl, I am not really an expert but I hope this helps:
When I am debugging in VS2010, I choose Debug --> Windows --> Local.
That Local windows stays there if I stop and Debug again.
You can also right click this window and choose "Dock as Tabbed Document", which makes it appear as a tab right next to the pages you are currently debugging.

Visual Studio Dual Monitor Layout : Watch/Debug Window keeps Popping on Left Screen

Every Time I launch a Debug Session VS 2010 pops the Watch/Debug Windows on the left Screen. I then move it manually to the Right One. After ending the session, going back to code, and relaunching a debug session, that damned Watch window pops on the left again. It turns me crazy ! Why isn't VS memorizing where I have put that window ???
Do you stop debug session with Shift+F5 or by quitting application which is being debugged? VS seems to forget window positions if debugging process was stopped by Shift+F5.
I tried the solution I found on this post. Did not work.
Seems like it's the exact same problem as with the find dialog (see this post)
Ended-up docking the heck out of the Watch/debug window into a more "stable" panel (Class view in my case).
This still looks like an annoying known bug in VS 2010. This sucks.
Visual studio 2010 has at least 3 screen modes.
Normal
Full
Debug
You should export the window settings after entering into the desired screen mode(in your case, debug).
Steps
Start 'debug' your project
Move the desired windows(watch/debug) to the 2nd monitor on right
Goto Tools>Import and Export Settings>Export selected environment settings>General Settings>Window Layouts and export it into a file.
Load the settings by using the import settings in the same window
Visual studio would remember your settings and would move the window to the 2nd monitor on the right, whenever you enter 'debug' mode.
As a tip, it is a great idea to create macros to load window settings and to assign keystrokes to switch between window modes, depending on the kind of development you are on.
code to create a macro to import a vssetting file:
DTE.ExecuteCommand("Tools.ImportandExportSettings", "-import:Path to VSSetting File")

Visual Studio - Is there any way to make the "Output" and "Error List" windows not appear after a debugging session?

It just occurred to me, after years of closing these two windows after a debugging session, that there may be a way to turn them off. I generally have the output window open while debugging and only check the error list periodically for warnings, and can always get to them if I want them anyway. Hoping someone else may know of a way to stop the default behavior?
Visual Studio remembers the window layout for coding and debugging separately, so removing the output window while you are debugging will not affect the "coding" state - you need to close the output window before you debug or it will reappear when debugging finishes.
In Tools>Options, Projects and Solutions, there are options "Always show error list if build finishes with errors" and "Show output window when build starts" which cause the error/output windows to be shown automatically just before you start debugging. These could be the culprits for adding an error/output window that then reappears when you exit debugging mode.
I have the output window "dockable" and pinned open. When I want to see it I use ctrl+alt+O, and to get rid of it I click into it and shift-escape. The output window "magically" disappears whenever I dont want it, but if I pay close attention I can see that I'm hitting the hotkey automatically myself :-)

Resources