问题
I'm using Visual Studio 2008 on a 64-bit version of Vista. After my program stops on one of my breakpoints, I can't step over or into the current line without either an Illegal Instruction exception or an Access Violation exception being thrown by my application. If I right-click on the next line and choose "Run to here" (equivalent to "Step over"), it works fine.
Addendum: there is nothing in any watch windows.
Also, here's something I forgot to mention: if I attach to the process, everything works just fine.
Has anyone run into this problem before?
回答1:
Mos, I was wondering have you resolved this problem (since I also have it with VS2005 and VS2008 on 64-bit Win7)?
Edit: "Uncheck Tools/Options/Debugging/Native/Enable RPC debugging" was suggested in comment, and seems to be the answer.
回答2:
Are you getting the exceptions in your application, or Visual Studio itself?
I would start by doing Clean on the entire solution then Build again. Sometimes if your binaries get out of sync you can get weird behavior when debugging.
回答3:
Is your application multithreaded?
In case it is:
Are you shure the Access violation is thrown by the thread that you are debuging ? Did you freeze all other threads?
回答4:
If you have any function calls in any of the watch windows, clear them out.
来源：https://stackoverflow.com/questions/836770/debugging-commands-step-over-into-cause-unhandled-exceptions