🚀 go-pugleaf

I've recently had some really nasty behaviour from CVW4. I don't know for sure
if it's CVW that's at fault, or if it's the compiler generating weird code,
but it's odd and very aggrevating to use nice words. This is what happens:

Tracing certain functions bombs CVW with this message:

				CVW4

               An error has occured in your application
      If you choose Ignore, you should save your work in a new file.
         If you choose Close, your application will terminate

                 [Close]              [Ignore]

The computer is then dead. The only traces of the CPU still running is that
pressing *-lock toggles the corresponding LED and moving the mouse around
works. C-A-D works too, and tells me "Windows has become unstable".

At first this problem occured in every function (C++ method) implemented in
one module only, but it's spread like a plague now. Tracing any function is
a gamble. Will it work, will it bomb? It's concistent, though. A function
that bombed once will always bomb. Of course I can step over them and analyze
the output, but I want to trace them, and I can't.

It might be some compiler bug, though. At one place there was a real bug.
A code fragment like:
   if (cond1 || cond2)
	return;

didn't work. The assembler code showed 3 jumps, all to the return.

The code:
    if (cond1)
        return;
    if (cond2)
        return;

worked.

Any ideas of what this might be? I don't have any fancy #pragma causing
weird things. I use the MFC to create a DLL.

Confused and clueless...
   _
/Bjorn.
-- 
Bjorn Fahller     Phone:              |The opinions above are not necessarily
Trollnasvagen 3A  Intl:+46 920 226870 |those of... Hey! Wait a minute. Do you
S-951 61 Lulea    Natl:0920-22 68 70  |seriously expect Me, a student, to carry
Sweden            << space for rent >>|the official voice of the University?