Visuall C++ Disassembly Window

Hi.

Everytime my application causes an access violation, the dissassembly window pops up. Or when I erroneously press the f11 key instead of f10. Is there a way I can turn this off ? I don't want to see the dissasembly code. I just want to see the offending function.
Please Help
WalluceAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
nietodConnect With a Mentor Commented:
This happens when there is no symbolic debug information for the code that is causing the error.  Like if the error occurs in a DLL compiled without debug symbols or if it occurs in the OS code and you haven't installed the debug version of the OS.    

There really isn't much you can do about it.   using programs and DLLs that have been compiled with debug information and Installing the debug version of the OS, available from MSDN, will help, but there is always some code somewhere that isn't going to have the debug symbols.
0
 
WalluceAuthor Commented:
I accept that, but can't I tell it NOT to bring up the disassembly window ? I am not going to change the windows code in assembly language anyway. I would like it to just show me the function in my program that caused the error. I really get frustrated when the assembly window comes up when I have not asked for it. It's a useful function, but bothersome. I have tried looking on the MS website, but I can't find anything. Is there anywhere on the site where I can ask a simple question like this, without being charged money ?

If you can, please answer these questions. I am, however accepting your answer, that I can not turn it off.
0
 
nietodCommented:
>>  can't I tell it NOT to bring up the disassembly window ?
I've never seen a way.   I guess they can't image a progrmmer not wanting to know _something_ about where the error is.  (even if it is next to nothing.)

You can dock the assembly window and make it small, so when it pops up it wil not take up much space.   Actually I guess you coudl just make it small.

>> I would like it to just show me the
>> function in my program
>> that caused the error.
Its not that smart.  it only knows where the function occured, now whose fault it was.  (Like if you passed a bad parameter to the function.)

You might already know this, but when this happens, you can use the call-stack at the top of the variables window to move back up the call stack to get to the function in your program that called the functions that failed.   this is not done automatically, but it is easy enough to do manually, I know I do it a lot!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.