Quote:Original post by Anonymous Poster
Well dufus, next time use CVS, Perforce, Source Safe, etc.

Well doofus, at least spell your insults correctly. ;) Anyway, how will that help? He already said his code isn't the problem.

Gee, I think alot of you didn't even read my first post. I told you that I had a backup from 2 days ago that I know for a fact worked perfectly, I tried that and it gave me the same error.

I have a feeling that either my compiler or computer is f*cked up.

Mastaba, my code will most likely run on MSVC6, but I forgot to mention that the game uses Clanlib which I doubt you have.

EVERY time have see something like this in my game it related to some other piece of code that I changed and overran a buffer, or used a wild pointer and generally destroyed my own stack. Here is the method I devised to work though the problem:

1) Backup your whole source tree every time you open the editor. Just replace the icon with a link to the batch file that later starts the ide. Backup on load is a pain but for me a life saver.

2) Write a small utility to add date to a filename(rename). So, Shooter.zip becomes Shooter Sun Jul 18 17_15_01 2004.zip. Add this to the batch file above.

I have a copy of my code from every time I have opened the game source dating back for about 3-4 years. I can rebuild the whole game to any point in that history. I have added a few tweaks like using 7zip's 7z.exe and excluding files I don't need. In total I only have about 40mb in my backup directory. Each backup costs me about 300k of disk.

Dir /s > New.txt on new source tree vs old source tree...etc. Use something like windiff to compare the differences. There is probably a better way to do this. This will tell you all the files that changes. My code has 627 small files, isolating changes. Then do a diff on the files that are different.

Ok. That’s helps isolating change to certain files. Other things to check:

-Ensure that you don't have bad data, ie include your data files in the above backups and version checking. I spent all day looking for a bug in my TTF code only to discover that my menu configuration file specified the wrong TTF file(which was not a ttf file :) )

-Binary search your code. Partition problematic code in half, if you can comment out the roots of great chunk of code. Once a section is found to fail, Copy the bits up smaller and smaller until you can work out what part of your game you can comment out without causing the crash. I do this second as it's less methodical and less likely to produce results. Occasionally just commenting out a big hunk of code will hide a problem rather than isolate it.

-Always leave your code in a compiling and running state before changing more stuff. I have a horrid habit of starting to fix something small and reengineering 3-4 critical subsystems at once at the end of it. My code will often not compile for weeks. Don't do this. I'm an idiot.

I didn't intend to solve your problem rather show you how to stop wasting time on this later, all learnt by wasting my time...

Gimp, most of your suggestions just seemed too much effort or I didn't get them.

I did comment out large swaths of code and actually got some results.

First I commented out my entire main loop except where it flips the back buffer and cleared the screen. This actually got the program to work, but all I had was a blank screen. Then I uncommented the part where it draws the player and that worked too.

I uncommented the next line where it did a function call that checked if the player had collided with a tile and that brought back the error. The weird part is when I deleted everything in the function and had it return 0 it still gave me the error.

Just for the hell of it I'll post my functions code and see if anyone sees something wrong with it.