Hope this helps... to be honest I just learned the existence of the crashinfo file just recently (lol). All the months I have been modding generals, I was almost always clueless and manually track that fuckin bug. But the harsh experience taught me a sort of "instinct" of what might have went wrong.
Hmmm. Let's see... Think about what specific event occured the moment just before the crash. Was it after you build "X" structure or maybe after you researched "X" upgrade or after you trained an "X" unit. After isolating the problem then try double checking the relevant ini codes for that "X"... maybe the commandset is pointing to a non existent commandbutton or maybe the commandbutton is pointing to a non-existent science/upgrade/unit etc. Doublecheck the names of your objects, modules, position of semicolons etc. a single character of a difference could mean debugging nightmare.
BTW, if you observed no specific event that occured before the crash, then maybe the one causing the crash is your AI opponent. Maybe the AI is doing something (building a structure, researching an upgrade, training a unit etc.) that causes the crash. If so, observe what faction is the AI playing? Is the crash specific to that faction alone, try to use it when you play and isolate the culprit.
One last tip, don't force yourself to immediately track the bug the first time, or even the second time you encounter it. Try to return after a few days, relaxation is the best ally of coders/debuggers.
And of course, please do regular backups of your .inis before you do coding. Reverting to an error free ini is the easiest way to solve the unsolvable. Just don't over backup your inis, you could be backing up an ini file that has a hidden bug on it you have not realized.
|