VC++ 5.0 Debugger crashing
Everytime I run a program that has an access violation, that forces me to Ctrl-Alt-Del it. Thats not the problem. After my program terminatesthe debugger wont shut down unless I Ctrl-Alt-Del VC. It says "This command will shut down the debugger. (Yes/ Cancel)." I pressed Yes, and all it does is showing a time glass icon, it doesn''t shut down the debugger. Anyone got any ideas?
-----------------------------
A wise man once said "A person with half a clue is more dangerous than a person with or without one."
-----------------------------A wise man once said "A person with half a clue is more dangerous than a person with or without one."The Micro$haft BSOD T-Shirt
The best way to shut down a program you''re debugging (if it''s possible) is to hit the "stop debugging" button or menu choice. This will prevent the problem you describe.
I realize there are some situations in which that isn''t possible.
I realize there are some situations in which that isn''t possible.
~ The opinions stated by this individual are the opinions of this individual and not the opinions of her company, any organization she might be part of, her parrot, or anyone else. ~
BEGIN SARCASM
Oh my God, all my problems are solved, thank you kind soul.
END SARCASM
Did I not explain that stop debugging NEVER works? If I didn't then:
It never works.
Sorry for any confusion.
-----------------------------
A wise man once said "A person with half a clue is more dangerous than a person with or without one."
Edited by - immaGNUman on September 15, 2000 9:16:40 PM
Oh my God, all my problems are solved, thank you kind soul.
END SARCASM
Did I not explain that stop debugging NEVER works? If I didn't then:
It never works.
Sorry for any confusion.
-----------------------------
A wise man once said "A person with half a clue is more dangerous than a person with or without one."
Edited by - immaGNUman on September 15, 2000 9:16:40 PM
-----------------------------A wise man once said "A person with half a clue is more dangerous than a person with or without one."The Micro$haft BSOD T-Shirt
Hey ImmaGNUman,
Turnabout is fair play
I know exactly what you are talking about...I''ve never been able to solve this problem, from within VC++. My solution (as I suspect you''ve done), is to bring up the task manager and kill the VC++ process.
Regards,
Dean M.
Turnabout is fair play
I know exactly what you are talking about...I''ve never been able to solve this problem, from within VC++. My solution (as I suspect you''ve done), is to bring up the task manager and kill the VC++ process.
Regards,
Dean M.
Are you in the middle of a DircetX PROG?
If you are you need to step through each line ( in debug mode)until you have set up the cooperative level.
Whats happening is that you have created a surface that sits in front of VC.
VC is sitting there (retry, abort, cancel dialog) waiting for some user input.
If you step through your initialisation VC (or DX) figures out that VC is in the back ground.
To be safe, just step through each line until you enter your render routine. Then you can hit F5.
DeltaVee.
--------------------------
Carpe Diem
If you are you need to step through each line ( in debug mode)until you have set up the cooperative level.
Whats happening is that you have created a surface that sits in front of VC.
VC is sitting there (retry, abort, cancel dialog) waiting for some user input.
If you step through your initialisation VC (or DX) figures out that VC is in the back ground.
To be safe, just step through each line until you enter your render routine. Then you can hit F5.
DeltaVee.
--------------------------
Carpe Diem
D.V.Carpe Diem
Imagnuman:
No, you did NOT state that shutting down the debugger doesn't work (by shutting down the debugger, I mean going to the Debug menu option and hitting "Stop Debugging" when you get the failure, which, on all machines that I've seen at least, will instantly throw you out of debugging mode and back into normal VC++ editing mode, and will shut down your app for you even if it's stuck. Unless, of course, you're in exclusive mode graphics-wise, but you didn't bother to specify that, now did you.)
Even if you HAD bothered to state that, there's no reason to be nasty to someone who is trying to help you. Try not being a jerk. It does wonders for your popularity.
-fel
Edited by - felisandria on September 16, 2000 3:38:32 AM
No, you did NOT state that shutting down the debugger doesn't work (by shutting down the debugger, I mean going to the Debug menu option and hitting "Stop Debugging" when you get the failure, which, on all machines that I've seen at least, will instantly throw you out of debugging mode and back into normal VC++ editing mode, and will shut down your app for you even if it's stuck. Unless, of course, you're in exclusive mode graphics-wise, but you didn't bother to specify that, now did you.)
Even if you HAD bothered to state that, there's no reason to be nasty to someone who is trying to help you. Try not being a jerk. It does wonders for your popularity.
-fel
Edited by - felisandria on September 16, 2000 3:38:32 AM
~ The opinions stated by this individual are the opinions of this individual and not the opinions of her company, any organization she might be part of, her parrot, or anyone else. ~
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement