Walluce
asked on
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>> 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!
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!
ASKER
If you can, please answer these questions. I am, however accepting your answer, that I can not turn it off.