problem in debugging MFC app
-
hi I have the following problems while debugging an MFC application. I am using VS 6. 1)If i set the breakpoints and debug ,in the variables window it displays the value {???} for some variables.Is it unicode or something like that? 2)Most of the values of the variables are displayed in Hexadecimal form(even though i turned it off in options of variable window ),how to see the usual integer values? 3)The flow suddenly breaks into Disassembly(which i don't understand too much).is there anyway to get around this problem? Thanx in advance Early to bed and early to rise,work like hell and advertise
-
hi I have the following problems while debugging an MFC application. I am using VS 6. 1)If i set the breakpoints and debug ,in the variables window it displays the value {???} for some variables.Is it unicode or something like that? 2)Most of the values of the variables are displayed in Hexadecimal form(even though i turned it off in options of variable window ),how to see the usual integer values? 3)The flow suddenly breaks into Disassembly(which i don't understand too much).is there anyway to get around this problem? Thanx in advance Early to bed and early to rise,work like hell and advertise
- the question mark typically means it cannot resolve the address for the variable. 2)odd, that should work. 3) breaking away from your code to disassembly typically means it is in code that is outside your program and the source is not provided elsewhere. This can happen with many runtime functions or library code. There is no way to prevent it unless you make sure you do not step edit into something that is outside of your app code.
-
hi I have the following problems while debugging an MFC application. I am using VS 6. 1)If i set the breakpoints and debug ,in the variables window it displays the value {???} for some variables.Is it unicode or something like that? 2)Most of the values of the variables are displayed in Hexadecimal form(even though i turned it off in options of variable window ),how to see the usual integer values? 3)The flow suddenly breaks into Disassembly(which i don't understand too much).is there anyway to get around this problem? Thanx in advance Early to bed and early to rise,work like hell and advertise
Hi. Look at the answer from douglasjordan, above. I just want to complete his answer on your 3:rd point: If you shift window in the workspace (with ctrl-tab), then you will get back to your code. Look at the green arrowhead (or possibly the line above it). That's where your program called the function that was shown i assembler.
-
Hi. Look at the answer from douglasjordan, above. I just want to complete his answer on your 3:rd point: If you shift window in the workspace (with ctrl-tab), then you will get back to your code. Look at the green arrowhead (or possibly the line above it). That's where your program called the function that was shown i assembler.
Further on the third point, you should have an option to display the Call Stack in a window (most likely View->Debug->Call Stack, or Alt-V,D,C). The current level will be highlighted. Trace down the call stack to the first routine that you recognize, and double-click there. This should pop up a window with your source code so that you can see where the offending call is being made. The nice thing about the call stack is that you can display different variables in the Watch Window, depending on where you are in the call stack. As you double-click to display a function at various levels in the Call Stack, Visual Studio reverts to that function's context, so you can display local variables. The Call Stack window also shows the parameters that are passed to functions, so you can see if something was sent that "broke" stuff. Bob Ciora