Home > Visual Studio > Visual Studio Debugger Not Showing Variable Values

Visual Studio Debugger Not Showing Variable Values

Contents

Please keep me updated about the status. BTW, this makes another perfect 'break' : int *p = NULL, i = 1 / *p; Kochise share|improve this answer answered Nov 20 '15 at 13:29 user3069988 163 add a comment| To watch values change in real-time, I use a log file: Add statements to my code, such that when I change the value of a variable I emit a new line My cat sat on my laptop, now the right side of my keyboard types the wrong characters Could someone explain what knot theory is about, exactly? http://wiiemulator.net/visual-studio/visual-studio-debug-hover-over-variable.html

Join them; it only takes a minute: Sign up Visual Studio Watch window greyed out? For this reason I didn't originally notice these funky breakpoints, although I wondered about the phantom stops in Session_Start() when starting the project, but when we took a look at the Thanks for your help in advance.  RSS Top 8 posts / 0 new Last post For more complete information about compiler optimizations, see our Optimization Notice. Here’s an example:Refreshing Watch values that are out of dateIn certain circumstances you might see a refresh icon (a circle with two arrows, or a circle with two wavy lines) when

Visual Studio Debugger Not Showing Variable Values

Why do solar planes have many small propellers instead of fewer large ones? Or is it? Hoes does one run debug as a service? Like the original poster, I believe the program is doing the correct calculations, but the Watch window is displaying the wrong values.

  1. Top Log in to post comments (name withheld) Fri, 10/05/2012 - 11:46 Annalee, My program is rather large and I haven't been able to come up with a suitable small test
  2. The phantom breakpoint in web.config most likely resulted in interrupted assembly loading, which in the course of debugging through the project startup appears to have been triggered in the debugger's assembly
  3. complex watches, conditional breakpoints, etc.) if only Microsoft Visual Studio 2012* is installed.
  4. Mon, 04/28/2014 - 11:49 I'm an idiot with an old version.  I now have Fortran Composer XE 13.0.3636.11 with Fee.dll version 13.0.2225.2.and it works perfectly.  Thanks for your help Top Log
  5. This prompted me to delete the breakpoints and lo and behold, the problem went away.

In more complex code with more scoped variables, I basically see a wall of red icons - nothing at all is evaluated. Anyway, I think you have your answer now. –ChrisW Jul 10 '09 at 17:19 add a comment| up vote 1 down vote What you're attempting to do is not possible in With replying to the notification mails you only send a message to the IDZ admin. Visual Studio 2015 Debugger Not Showing Variable Values But here is what it looks what ended up solving it.

Did we miss something in the simplified test? All of the variables are Real(KIND=8). Finally we have an extension to the debugger - Fortran Expression Evaluator - which may be involved. Please open a Premier issue with more specific information (alternatively, you can reply with a private message, and attach your code).

I was using VS 2012 previously, and depended largely on being able to hover over and expand local variables to look at their values. Visual Studio 2015 Watch Window Can you attach a copy of a program that reproduces the debug problems so I can investigate the issue? No response for Integrating Cos[2 pi x/l]/( t^2 + x^2) Utensil that forms meat into cylinders How do I get the last lines of dust into the dustpan? How not to lose confidence in front of supervisor?

Visual Studio 2013 Watch Window

Learning resources Microsoft Virtual Academy Channel 9 MSDN Magazine Community Forums Blogs Codeplex Support Self support Programs BizSpark (for startups) Microsoft Imagine (for students) United States (English) Newsletter Privacy & cookies http://stackoverflow.com/questions/1110521/visual-studio-watch-window-greyed-out I'm not sure what "fee.dll" is...if you can describe its location, I can look at its version number as well. Visual Studio Debugger Not Showing Variable Values Regards, Annalee Intel Developer Support Top Log in to post comments David White Wed, 10/17/2012 - 16:48 Thanks, Annalee. Visual Studio Debug View Variables Rick Strahl April 28, 2014 # re: Visual Studio 2013 'Could not evaluate Expression' Debugger Abnormality @clau137 - yes it probably is related to the multi-threaded stacks.

more hot questions question feed default about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation http://wiiemulator.net/visual-studio/visual-studio-2008-debugger-not-working.html Claudio March 26, 2014 # re: Visual Studio 2013 'Could not evaluate Expression' Debugger Abnormality It simply works like that! I don't know whether that makes any difference. Not sure if that is a config setting, since it never worked for me in VS2012. Visual Studio Watch Variable

Hence, VS might be broken if (some) DLLs cannot be loaded. The variable which I am watching is in the scope and it has value. it works for me :) share|improve this answer edited Apr 19 at 9:44 Shree Krishna 4,65341340 answered Apr 19 at 9:24 Aftab Ahmad 6110 add a comment| Your Answer draft http://wiiemulator.net/visual-studio/debugger-not-working-in-visual-studio-2008.html Anyone know the premise of this pcb assembly note?

What different frame materials have been used? Watch Windows Excel How can I find the perimeter of a concave pentagon? Did the Gang of Four thoroughly explore "Pattern Space"?

Consider making a small donation to show your support.

Contradiction between Analytic and Numerical Integration Can leaked nude pictures damage one's academic career? Storing passwords in access-restricted Google spreadsheets? the generated debug information), the debugger itself - this is less likely as the differences occur after installing the v13.0 FORTRAN tool [with the same VS2010]. Visual Studio Add Watch Greyed Out If it still reproes, please get us a repro project and steps (either connect or the feedback tool that's integrated in VS now).

It appears that Fortran Expression Evaluation (FEE) extension that comes with our Intel(R) Fortran Composer XE 2013 products does not work for Microsoft Windows Server 2008* (and Microsoft Visual Studio 2012*). Lets say you are receiving thousands of data packets per sec, if instead of simply incrementing a counter, you write a line to a log file, the system will fall over. a "debug build" you mean? –Assaf Lavie Jul 4 '09 at 18:15 add a comment| up vote 1 down vote I got the exact same problem. navigate here This capability is forfeited w/ the Module structure.

Yes No Additional feedback? 1500 characters remaining Submit Skip this Thank you! This is true of essentially any debugger I've worked with in the past. it then loaded all symbols made a clean build, removed it again and enabled just my code clean build, voila i got correct debug symbols again! North by North by North by South East StackList implementation Why is nuclear waste dangerous?