Let's do some debugging

[Saffith]

Updated to build 1317, and modified to work through the launcher. This shouldn't require any additional effort anymore.

[Saffith]

Updated to 1329.

[Saffith]

And again. 1340 now.

[XMuppetSB]

Okay, I found a fatal bug that sometimes causes ZC to instantly crash every time you continue on the last DMap you saved your game on.
PS: I have never done any debugging before. Furthermore, I think that the way ZC is as of late, it really is becoming increasingly unstable because of random crashes, including fatal crashes that happen every time you start a quest. Besides, allegro is just about the most unstable thing you could possibly use when making EXE programs!
EDIT: I think the fatal quest start-up crash may have to do with the fact that the DMap I saved my game on has a title that is displayed when the player first enters the DMap. However, it only occurs sometimes. Note that the DMap I last saved my game on had a a save point combo and a save and quit combo, and was set to 'Continue Here', with the Save-Continue Screen Flag checked on the screen where Link would start/continue on that DMap.

[Saffith]

PS: I have never done any debugging before.

All you have to do is run the game normally and post gdb.log whenever it crashes. That tells us where in the code it happened, which is what we need to know to fix it.

[Imzogelmo]

OK, I've been using RC2 for a while but I just had 2 crashes in ZQuest this afternoon-- any chance of a new debug build so I can help track this down?

[Saffith]

It would take a It would take some time to get them set up again. It could be something easy, though; what were you doing when it crashed?

[Imzogelmo]

It was different in each of the (now 3) times, but the similarity was that I was drawing a screen (relative mode if it matters) and then exited (once just by exiting, another time by opening another quest, the third time I'm not sure).

EDIT: Now the 4th crash today, and this on different quests. I'm pretty sure I can re-create this if needed. I'm getting an access violation at 0x7C910A19.