• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 332
  • Last Modified:

Having problems with visual studio 2005 debugger.

Hey experts how is everything.
I ve been having problems with my visual studio debugger...I reinstall visual studio twice already.
Well here is the scenario...usually when I run my program (F5) or just go to debug the program runs fine..but as soon as it hits an error everthing just freezes..the debugger doesnt fire up or nothing...and the only way i can actually see the error that it gives is only for a breef second when I hit "Alt + Control + Delete" to log off.

now I though maybe its my code or something..so I would deliberately make another window application and misspell a variable and try to run it...and yet still visual studio freezes up and the only time im able to see the error if i try to log off the computer.

Is there a way to check if the debugger is working correctly?
0
saruman101
Asked:
saruman101
  • 5
  • 2
1 Solution
 
saruman101Author Commented:
To keep things updated I try to make my own error to see if the debugger fire up and eventually it didnt.
Example I did this to see if I can get it once the program runs

///
Dim A as integer = ""
//
this eventually the debuggers see and stops the program from running..but instead it doesnt..and again I still face the same problem again..where I need to log off.

Is there any way to make sure the debugger is running before I compile and execute my program.
0
 
VoteyDiscipleCommented:
What's confusing is the changes you mentioned to deliberately cause runtime errors sound to me like they should have triggered compiler errors.  Did I misunderstand that?  Does the code compile correctly, but when an exception is thrown Visual Studio tanks, or is it that even a compiler error remains a mystery until you've restarted?
0
 
saruman101Author Commented:
Thanks for responding..well like I said when I made that error deliberately the debugger doesn't shoot off...and let say for example another error that could occur during runtime even that does not shoot off the debugger....is there anyway through visual studio to find out if it is just not installed..or if there is a way to activate the debugger...because all the time that I try to compile and run, if it is not running it wont catch anything...

Hell its like having a try block with catch and even that doesnt do nothing , nada, zippo.

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
VoteyDiscipleCommented:
Sorry, I don't think I phrased my question very clearly.  If you make a deliberate SYNTAX error, does the compiler still catch that?  Or is this only applicable to runtime errors that ought to be handled by the debugger?

I'm trying to determine the scope and extent of the problem.
0
 
saruman101Author Commented:
sorry I should of been more clear .
No I'm talking about runtime errors.

Here I will give you another example
Let say I'm making a connection to an access database.
Now let say I'm declaring an OLEDBCOMMAND ,but I never made a new instance of that object...along the way I make everything else..the connection,SQL statement, etc etc..
Now Mind you since I didnt make a new instance object of the command it would still run...but since I know it will give me an error during runtime the debugger never shoots off to tell me "Hey this line..this code does not make sense etc etc ",
instead the whole visual studio freezes and when and ONLY when I decide to log off my computer I then shows me the debugger catching the error for a brief second and of course then im log off.

Also the error I said I made deliberately
which is
Dim A as integer = ""

Let say that instead I made it into 1
and somewhere along runtime within a text box I decide to pass this value to it "" (blank)..therefore, this the debugger should catch as well...yet it freezes..and again only when I hit ctrl + alt + del
and I choose to either log off or shut down I see the debugger briefly for like 2 or 3 seconds and well you get the idea what happens after that.

 
0
 
saruman101Author Commented:
I just reinstalled Visual studio for the 3rd time and I still get the same error.
Is there a way to know if the debugger is being stopped or not running when I start up Visual Studio 2005?
0
 
saruman101Author Commented:
Hey I figured out the problem believe it or not, it was my anti virus program.
For some reason everytime I disable my antivirus program the debugger works just fine.
But if I restart my machine and have the antivirus running as soon as windows boot up it gives me the same error that I had the last time.

Now for some crazy reason if I disable my anti virus and run my visual studio 2005 and then load it up again things work fine.
To tell you the truth I don't know why it happens , but I'm happy it works :)

0
 
Computer101Commented:
PAQed with points refunded (200)

Computer101
EE Admin
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now