Damn corrupt files!

[bignobody]

Gah! Just wasted several valuable hours tracking down a problem that wasn't even my fault.

I was play-testing, and found a situation that had previously worked without trouble. Now it would hang every time. I hadn't touched this area in a while, so I was kind of stumped as to why this was happening now.

So I archived the project, and rolled back to previous versions until the problem wasn't present (two versions previous). "Easy." I thought, "I'll just load up WinMerge and check the differences, and the problem should be obvious."

Wrong. None of the code changes seemed like they could cause a hang. So I rolled forward to my current version, and dropped in the files that had changed from the older working version, and recompiled.

And the hang still occurred.

So, I rolled back to the previous working version, then merged in the changes from the latest version. Recompiled, and the hang is gone.

All I can figure is that there was some VC project file that had become corrupt, but not enough to prevent compiling.

Anything like this ever happen to anyone else?

[Nils Pipenbrinck]

Anything like this ever happen to anyone else?

Jep. Sometimes Visual Studio Whatever just compiles and links big bullshit together.. That usually happends when I really stress the edit and compile feature along with precompiled headers.

A rebuild all usually fixes all problems.

Also - if you want to save yourself several hours of useless debugging: don't ever try to use unicode fonts as your editor-font in visual studio. This can lead to strange fuckups and corrupt sourcecodes.

[bignobody]

Glad I'm not alone in my pain ;)

Actually I did a clean and rebuild all each time when I was trying to get to the bottom of the problem, but it didn't help this time (though I have had it work with previous problems).

I've never changed the IDE font from the default (using VC ++ 2003 standard), so hopefully they don't use a unicode font by default :blink:

Hey! I just hit a milestone here. My 100th DevMaster post :w00t:

Regards,

[Alex]

Yeah..that's one of the really scarry things about MSVC.NET...
You get corrupt debug data or a crash..do a full rebuild and it is gone. Well..that's no guarante that the crash was caused by .net..the error might still be there. It just might not show up just now...

Alex

[Apocalypse]

I always get this kind of error when I modify the members of a class in a header file.

Rebuild fixes all!