- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for all your help in getting proper speed of Visual Studio under Win XP. Deleting the NCB and OPT files did it under both Home and Pro.
One last thing to get fully up to speed on this new machine. I cannot get to the debug mode when my program crashes as I could do under Win 98 SE.
When an exception occurs, I get a Visual Fortran runtime error and a list of file names, program and subroutine names and line numbers. I press OK.
Then I get a message box saying my program has encountered a problem and needs to close... My choices are Debug, Send Error Report and Don't Send. I select Debug. (under Win 98 SE, it is debug or close).
Then I get a message saying my program name and some details and "Application Error". The exception Array bounds eceeded. It gives me a Hex address and says "Click on OK to terminate the program." I press OK, which is the only option.
I get a message box from Compaq Visual Fortran saying one or more breakpoints are positioned on invalid lines and then have been moved to the next valid line. It appears I am about to enter the debugger. I press OK.
Now, rather than being in the debugger where I can look at variables and see what is wrong, I am back in the edit mode.
Suggestions welcome. You have been helpful before.
Charles.
One last thing to get fully up to speed on this new machine. I cannot get to the debug mode when my program crashes as I could do under Win 98 SE.
When an exception occurs, I get a Visual Fortran runtime error and a list of file names, program and subroutine names and line numbers. I press OK.
Then I get a message box saying my program has encountered a problem and needs to close... My choices are Debug, Send Error Report and Don't Send. I select Debug. (under Win 98 SE, it is debug or close).
Then I get a message saying my program name and some details and "Application Error". The exception Array bounds eceeded. It gives me a Hex address and says "Click on OK to terminate the program." I press OK, which is the only option.
I get a message box from Compaq Visual Fortran saying one or more breakpoints are positioned on invalid lines and then have been moved to the next valid line. It appears I am about to enter the debugger. I press OK.
Now, rather than being in the debugger where I can look at variables and see what is wrong, I am back in the edit mode.
Suggestions welcome. You have been helpful before.
Charles.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I were you, I would
slect 'debug' as the active configuration
delete all my breakpoints
recompile and rebuild the debug version
add in breakpoints as needed,
start the debugger..
hope for the best...
regards
AR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Running in debug mode with no breakpoints set does actually work in that if you crash, you are in the debugger and can look and see what is going on.
On Win 98, however, you can run in normal mode and switch to debug when a crash occurs. For some reason Visual Studio is not allowing for that in the Win XP Pro setup.
Shouldn't it?
On Win 98, however, you can run in normal mode and switch to debug when a crash occurs. For some reason Visual Studio is not allowing for that in the Win XP Pro setup.
Shouldn't it?

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