Home > Visual Basic IDE > Visual Studio Debugger Not Working

Visual Studio Debugger Not Working

Hi I have installed VS2008 in my machine. I made a small program in the VB. When I start debugging, the system responds by indicating that the program is running but I don't see any output. Is their a possibility that VS2008 debuggers woun't work with Windows XP Home Edition which comes with my laptop.

ahmarsk Wednesday, November 18, 2009 5:32 PM

Do you, by chance, have a Kensington pointing device (mouse/trackball)?
I had this type of problem and turned out the Kensington software that came w/ my trackball is not compatible w/ Visual Studio (I have 2008).
There is a thread somewhere in these forums (maybe in C#) that describes this issue.

Once I removed the software, VS2008 started debugging and running applications fine.

Marked As Answer byJeff ShanMSFT, ModeratorThursday, November 26, 2009 6:44 AM

BarbaraR Monday, November 23, 2009 5:36 PM

Hi ahmarsk,

As jwavila and Rod said, VS 2008 can run well on XP Home edition. BarbaraR's post also could be the cause.
Besides, please try to enable JIT optimization to see whether your code could run.
1. choose Tools ->Options
2. select Debugging->General
3. uncheck option "Suppress JIT optimization on module load"

Hope this helps

Regards
Jeff Shan

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Marked As Answer byJeff ShanMSFT, ModeratorThursday, November 26, 2009 6:45 AM

Jeff Shan Wednesday, November 25, 2009 5:50 AM

And exactly what output are you expecting? Meaning, what is your program supposed to be doing.

I run VS2008 on a couple of mine with XP Home and don't have any problems.

jwavila Wednesday, November 18, 2009 5:48 PM

It should work. Try making a Windows Forms application. When you run it, you should see a blank form appear.

Rod
www.vb-helper.com

Rod Stephens Saturday, November 21, 2009 3:03 PM

When the debugging starts I get the following message:

Attempted to read or write protected memory. This is often an indication that other memory has been corrupted.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory has been corrupted.

How do I fix this problem

ahmarsk Monday, November 23, 2009 4:50 PM