Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29249 Discussions

help- Is there a debug Memory window and how to access it.

anthonyrichards
New Contributor III
1,233 Views
In DevStudio+CVF, there was an option under View to see a list of Debug Windows such as Memory, call stack, Registers. In particular I used to like to look at memory locations by watching the LOC of a variable and pasting the value into the memory window.

I cannot find a similar facility in the VS+IVF Composer set-up, probably because of my unfamiliarity with the new set-up. Is there one? what about call stack and registers also?

Also, I would appreciate guidance as to how to achieve and maintain a particular tidy tiling of all the windows that can be open when editing files and debugging, as I find floating windows are a bit like slippery fish that dash for cover to one edge or another uncontrollably when you try drag them around, or else they zoom out to fill half the screen and cover everything else!
0 Kudos
10 Replies
mecej4
Honored Contributor III
1,233 Views
I am a reluctant user of GUIs and VS, but I can answer the question in your first paragraph. Put a breakpoint at the first executable statement in your program (or another place of your choice) and run the program. When the breakpoint is hit, you can go to Debug->Windows and activate the windows that you want.
0 Kudos
anthonyrichards
New Contributor III
1,233 Views
There is still no 'emory' window available.
0 Kudos
Steven_L_Intel1
Employee
1,233 Views
There are actually four memory windows available, but you can see this only while the debugger is running.

0 Kudos
mecej4
Honored Contributor III
1,233 Views
It took me a while to grasp the evanescence of these windows.

At first, given the large number of menu choices and combinations, I blamed my weak memory when I failed to find a window that I had seen before. Then, more or less by accident, I discovered that a useful thing to do with any new debugging job was to open the main source file and place one or more breakpoints in it and hit "go", just to be able to access the other windows.
0 Kudos
anthonyrichards
New Contributor III
1,233 Views
Well, I have VS2005 running on Windows XP Pro, and this is what I see: No Memory Windows...
0 Kudos
mecej4
Honored Contributor III
1,233 Views
I don't have VS2005, so this is a guess, but won't take much effort from you. Click on the "Disassembly" tab first, and then try Debug->Windows. Do you see "memory", "registers", "stack", etc. ?
0 Kudos
anthonyrichards
New Contributor III
1,233 Views
Nope, it just gives me disassembled code listing; no resizable window with an edit box on the top line where I can type in a memory location and a listbox below it that then displays a slice of the memory starting from the typed-in Hex address and with an ASCII translation of the bytes running down the side. Woe is me!
0 Kudos
IanH
Honored Contributor III
1,233 Views
Curious. I run VS2005 (professional and standard on different machines), and the Memory sub-menu is in the Debug > Windows menu just above Disassembly.

Can you see it/restore it via the Tools > Customize command (on the Commands tab under the Debug category)?

Something else to try - in the command window (under View > Other Windows here) you can type "memory" (or memoryn) to bring up the (n-th) memory window.
0 Kudos
jimdempseyatthecove
Honored Contributor III
1,233 Views
My VS2005 on XP had Debug | Windows | Memory
But I recently upgraded to VS2010

What you will need to do (I cannot step through instructions here so I will sketch it for you) is

Starta debug session (do not do this in edit session) then

Tools | Customize | Commands tab | Debug catagory

Then drag commands elevator down to Memory 1, 2, 3, 4

Click and drag Memory 1 over to main ide window Debug, this will open, then hover over Windows, this will open, find a spot where you would like to see the Memory 1 option, and release the mouse button (drop the icon). Repete this for the other Memory window.

It is important you do this form a Debug session since the menu layouts of the edit session are different from those of the Debug session.

BTW you can also drop the icon(s) onto the tool bar as well.

Jim Dempsey
0 Kudos
anthonyrichards
New Contributor III
1,233 Views
Many thanks Jim, that did it! I dropped the icon onto a tool bar. It opens fine.
0 Kudos
Reply