VS debugger stopped working

  • Thread starter Thread starter Mikael Östberg
  • Start date Start date
M

Mikael Östberg

Hello all!

I have been working on a project for some time now and yesterday, my
debugger stopped working.
It is a class library which I run from a Win32 test app, so no IIS involved
at this point.

I can still set breakpoints and when debugging the breakpoints get hit -
just like it would work normally.

However, when I want to check values of objects and such using autos or
watch, all values are null. I can step through the code, but it seems like
the debugger does not care about the code. It steps into catch blocks even
though an exception would be impossible. It would even step into this
statement:

string test = null;
if(test != null) {
// it would step into here
}

Here is an image that proves this wierd condition:
http://www.inloop.se/temp/debugger.jpg
This example is a standard Win32 app with only one form and one button.

I have run the repair feature in Visual Studio. I have also re-installed the
..Net framwork 1.1 SP1 for Win2003 but that didn't help.

Has anyone seen this before? What could possibly had happened and more
importantly, how can I solve this?

Thanks!

Mikael Östberg
 
Hello!

Thanks for your answer!

It is set on DEBUG.

Note that this is a standard C# Windows project. I only added the button and
the code and made no more changes.

The same thing happens in VB.Net.

I have read forums all day and no one seems to have had the same problem.

Any clues?

::m
 
Hello again!

I tried to debug an old ASP.NET project and there it works fine.

This narrows this wierd issue down to Win32 apps.

Clues anyone..?

::m
 
Either:
You have debugging disable in project settings
or
You debug file/s (*.pdb) are out of sych. (usually this result in debug row
looks funny or breaks on empty line)

Check for build errors or file lock errors.

Try Rebuild vs Build (Seems to unlock locked files)
Sometimes you have to reboot...

Schneider
 
Back
Top