MSVC 2003 break point problem

I have run across a problem trying to use break points in MSVS 2003 to debug my code. I don't see anything wrong with my code and the debugger says MBRet = 7 and it also says IDNO = 7. Anyway when I try to step through my code these lines are skipped:

Code:

---

if (MBRet == IDNO)
{
    WC.bFileNeedsSaved == false;
}

---

Just for kicks heres is the function I am using the return value of:

Code:

---

int AskAboutSave (HWND hwnd)
{
    int iReturn = NULL;

    iReturn = MessageBox (NULL, "Save current changes?", szAppName, MB_YESNOCANCEL);
    if(iReturn == IDYES)
    {
        SendMessage(hwnd, WM_COMMAND, ID_FRAME_SAVE, 0);
    }
    return iReturn ;

---

I have tried 'cleaning' the solution but no change. I really don't see anything wrong with this code!

Here is the code where Visual Studio just deletes my break points and skips the code.

Anyone ever seen anything like this?

1. check that you do not have any optimization enabled
2. try to clean and rebuild all

Update I have done what you suggested and even rebooted.

Here is another part of my code that reuses this function and it allows me to step through just fine:

Code:

---

    case WM_CLOSE :
        if(WC.bFileNeedsSaved)
        {
            test = AskAboutSave(hwnd);


            if (test == IDCANCEL)
            {
                return 0;
            }
            else if (test == IDYES)
            {
                SendMessage(hwnd, WM_COMMAND, ID_FRAME_SAVE, 0);
            }
            else if (test == IDNO)
            {
                MessageBox(hwnd,"test","test",IDOK);
            }
        }

---

I even rebuilt the project on another pc to the save effect. It still wont let me debug the ID_FRAME_NEW case.

I am at a loss here. What else can I do besides a clean rebuild?

I finally found a somewhat related link that suggests reinstalling MSVC but since I have the exact problem on a different PC I can't see how this could fix it and that's a pain in the butt!
Still Googling :( hopefully I'll find an answer.

After closer inspection of this line of code...

Code:

---

WC.bFileNeedsSaved == false;

---

Well I feel like an idiot maybe I shouldn't try programming until 2:30 in the morning.


;)

The only reason I caught the mistake is because I retyped it without cut and paste! Walla, I didn't make the same typo.

I see the current line of code jump around alot in MSVC 2003, especially when using exception handlers (try/catch)

It often looks like it hit the last line of the method and then jumps back to the last line of the catch().