Look at this small piece of stack frame:
There are two local variables:
_lrct$ = -212 ; size = 16
tv5476 = -204 ; size = 8
Later this command rewrites 8 bytes of _lrct$
fst QWORD PTR tv5476[ebp]
This is how compiler of Visual Studio 2005 builds release version (debug version works properly). My question is: if this defect presents only in my exemplar of 2005, damaged for some reason (once something like this happened- a "new" operator
refuses to allocate memory at all and only re-installation of 2005 fixed the problem) or I have to throw 2005 away and replace it by something newer?