- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I think I inadvertently changed some setting in my compiler and I don't know how to get it working right again. I am using VF 11.1.051 with the integrated VS 2008 shell.
However the settings were changed, I know that they must have changed through the top level GUI, I did not go in to any menu options like tools > options.
My first symptom what that when I set a breakpoint and started debugging, all of the local variable values that were shown had # signs and nonsense values. I turns out these were hex values. I stopped debugging and turned off the hex display using the debugger toolbar button (the icon is between "step out" and "show threads in source" buttons). Now when I run the debugger, it is very slow and after I reach a breakpoint, if I hit "step into", the next step takes a longer amount of time than expected, and three things flip back and forth in the gui: The "Hex" toolbar button flicks on and off, the process listed in the "debug location" toolbar flicks back and forth between the expected process and some other value, the other value definitely has some hex number in front of it, and the "Thread" item in the debug location toolbar also flicks back and forth.
Can anyone help me determine what has changed with my settings to cause this? I have already rebooted.
Thanks,
Ben
I think I inadvertently changed some setting in my compiler and I don't know how to get it working right again. I am using VF 11.1.051 with the integrated VS 2008 shell.
However the settings were changed, I know that they must have changed through the top level GUI, I did not go in to any menu options like tools > options.
My first symptom what that when I set a breakpoint and started debugging, all of the local variable values that were shown had # signs and nonsense values. I turns out these were hex values. I stopped debugging and turned off the hex display using the debugger toolbar button (the icon is between "step out" and "show threads in source" buttons). Now when I run the debugger, it is very slow and after I reach a breakpoint, if I hit "step into", the next step takes a longer amount of time than expected, and three things flip back and forth in the gui: The "Hex" toolbar button flicks on and off, the process listed in the "debug location" toolbar flicks back and forth between the expected process and some other value, the other value definitely has some hex number in front of it, and the "Thread" item in the debug location toolbar also flicks back and forth.
Can anyone help me determine what has changed with my settings to cause this? I have already rebooted.
Thanks,
Ben
Link Copied
12 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I also pressed the "Show SSE registers" button to see what would happen. This popped up in that window that contains items such as "locals" and "call stack". I have since found the tab containing the SSE information, and I right clicked on it and selected "Hide." The system is still acting funky.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it possible you turned off the debug information either by buildind a RELEASE build or by removing the /Zi switch from the command line switches?
------
Wendy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I think you may be on to something. In my Property pages, the compilation "command line" I see is: /nologo /debug:full /Od /heap-arrays0 /gen-interfaces /warn:interfaces /real_size:64 /module:"Debug\TempFiles\" /object:"Debug\TempFiles\" /traceback /check:bounds /libs:static /threads /dbglibs /c
On my Linker Command Line, I have this: /nologo /debug:full /Od /heap-arrays0 /gen-interfaces /warn:interfaces /real_size:64 /module:"Debug\TempFiles\" /object:"Debug\TempFiles\" /traceback /check:bounds /libs:static /threads /dbglibs /c
This is all set in my Debug properties, and Debug is my currently set as my selected build.Do you know how I could get the switch to show up?
I'm kind of concerned about the "hex" menu item flashing on and off, I don't think that's normal.
On my Linker Command Line, I have this: /nologo /debug:full /Od /heap-arrays0 /gen-interfaces /warn:interfaces /real_size:64 /module:"Debug\TempFiles\" /object:"Debug\TempFiles\" /traceback /check:bounds /libs:static /threads /dbglibs /c
This is all set in my Debug properties, and Debug is my currently set as my selected build.Do you know how I could get the switch to show up?
I'm kind of concerned about the "hex" menu item flashing on and off, I don't think that's normal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actually debug:full should be the same as /Zi, so that it is not the source of the error. Let me look into this somemore.
Wendy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you try an uninstall of the Intel Visual Fortran (including the Integrated Development Environment) through Add/Remove Programs and then do a Microsoft Visual Studio Repair, and then finally install the Intel Compiler?
We have not seen this behaviour before and suspect some sort of corruption in the IDE integration.
Thanks,
Wendy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you, I will try this and report back. Something else that has started happening is when I run debug and then stop the program before it is completed, sometimes the dosbox will remain open showing the program output, and I won't have a way to close it other than to reboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Wendy,
In my Add/Remove Programs I have several copies of Intel Visual Fortran Compiler Professional Edition 11.x.xxx. So I will uninstall all of those.
Other than that, I have "Microsoft Visual Studio 2008 Shell (Integrated mode)" - would you suggest I repair or uninstall/reinstall this?Should I look for any other entries?
Thanks,
Ben
In my Add/Remove Programs I have several copies of Intel Visual Fortran Compiler Professional Edition 11.x.xxx. So I will uninstall all of those.
Other than that, I have "Microsoft Visual Studio 2008 Shell (Integrated mode)" - would you suggest I repair or uninstall/reinstall this?Should I look for any other entries?
Thanks,
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ben,
Yes I think I would uninstall the VS 2008 shell too. It should re-install with the compiler.
Yes I think I would uninstall the VS 2008 shell too. It should re-install with the compiler.
------
Wendy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Wendy,
I uninstalled all of my 11.1 revisions and the visual studio 2008 shell. I rebooted and reinstalled 11.1.051 IA32 with shell. All of my settings seem to have been kept intact.
The problem seems to have gone away. Debug processing seems to be much quicker. When I hit a breakpoint and continue (F11), the information bars I noted in my original report no longer flicker between values. This is much faster. I hope this doesn't happen again, though, as it takes a bit of time to run the uninstaller and then reinstall.
Regards,
Ben
I uninstalled all of my 11.1 revisions and the visual studio 2008 shell. I rebooted and reinstalled 11.1.051 IA32 with shell. All of my settings seem to have been kept intact.
The problem seems to have gone away. Debug processing seems to be much quicker. When I hit a breakpoint and continue (F11), the information bars I noted in my original report no longer flicker between values. This is much faster. I hope this doesn't happen again, though, as it takes a bit of time to run the uninstaller and then reinstall.
Regards,
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Glad to hear it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for letting us know the re-install worked. In summary, there are no debugger settings that would have caused this behavior and we suspected the Debugger IDE integration was somehow corrupted, hence the suggestion to re-install.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page