Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

secret combo crash

10 replies · 2,293 views · Started 16 March 2010

secret combo flag 17 is crashing me
built a new screen, tried setting the flag 3 times it crashed 3 times

Jman, am sending the user.dmp addy to you in a PM

ok this is consistant
every time I try to place secret combo flag 17 it crashes, even after rebooting and starting fresh

here is the log as well, if it's of any use

ZQuest v2.11 Beta (Build 18)
Allocating tunes buffer (16.00k/16.00k)... OK
Allocating map buffer (1.11M/1.12M)... OK
Allocating combo buffer (5.98k/1.13M)... OK
Allocating string buffer (10.62M/11.76M)... OK
Allocating door combo buffer (159.50k/11.91M)... OK
Allocating dmap buffer (234.00k/12.14M)... OK
Allocating combo buffer (1.62M/13.76M)... OK
Allocating color data buffer (314.11k/14.07M)... OK
Allocating tile buffer (511.88k/22.56M)... OK
Allocating tile grab buffer (511.88k/31.06M)... OK
Allocating trash buffer (97.66k/31.16M)... OK
Allocating item buffer (31.00k/31.19M)... OK
Allocating weapon buffer (2.50k/31.19M)... OK
Allocating guy buffer (28.00k/31.22M)... OK
Allocating combo class buffer (32.17k/31.25M)... OK
Allocating combo undo buffer (1.62M/32.87M)... OK
Allocating new undo tile buffer (511.88k/33.37M)... OK
Resetting new tile buffer...OK
Allocating file path buffers (14.00k/33.38M)... OK
Initializing Allegro... OK
Loading data files:
Fonts.Dat...OK
ZQuest.Dat...OK
QST.Dat...OK
SFX.Dat...OK
OK
Initializing sound driver... OK
gfx mode set at -1 8bpp 800 x 600
Loading Quest...

Decrypting...okay.
Opening...okay.
Reading Header...okay.
Made in ZQuest 211 Beta 18
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Misc. Colors...okay.
Reading Game Icons...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Combo Aliases...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading Tunes...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Custom Guy Data...okay.
Reading Custom Link Sprite Data...okay.
Reading Custom Subscreen Data...okay.
Reading FF Script Data...okay.
Reading SFX Data...okay.
Reading Item Drop Sets...okay.
Done.
Loading Quest...

Decrypting...okay.
Opening...okay.
Reading Header...okay.
Made in ZQuest 211 Beta 18
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Misc. Colors...okay.
Reading Game Icons...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Combo Aliases...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading Tunes...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Custom Guy Data...okay.
Reading Custom Link Sprite Data...okay.
Reading Custom Subscreen Data...okay.
Reading FF Script Data...okay.
Reading SFX Data...okay.
Reading Item Drop Sets...okay.
Done.

Strange... I've been able to place flag 17 on the screen without ZQuest crashing on me... In fact, it never crashes on me when I place flag 17 on the screen. Maybe it's just a compiler bug on your end! Those compiler bugs are easily the single hardest ones to track down, you know, and they return sooner or later!😛

it crashes every time on me, and is now crashing going into the tile pages as well
I've crashed 5 times in 20 minutes

2 crashes trying to get into the tile pages
4 crashes on flag 17
and one other crash that I'm not certain what I was doing then.

it seems to be getting worse, and rebooting didn't change anything

Hopefully it didn't corrupt my quest

It almost seems this is only happening on layers, the flag 17 that it won't allow me to place does work on layer 0 but not 1
the map is #55 screen 40 and layer one is map 56 screen 40

I'm pretty sure I fixed the issue regarding showing flags on layers.

Not sure about the tile page crash you mentioned though. If you can induce another crash and send the dump file that'd be helpful.

Nah, the flag one's new. Should be easy enough, null pointer in zmap::drawcolumn(). Looks like there are a few of those, or at least uninitialized pointers, being used in drawcolumn() and drawrow().

What?! Uninitialized pointers? In ZQuest? O: Not on my watch!! ..*shoots self in the face* ..

Seriously though, this is getting ridiculous. I haven't duplicated this yet.... Let me fire up gcc...

Wait sorry, you all must have misunderstood me. I found that bug and fixed it already last night is what I meant. I'm just curious about the tile page one.

The tile page crash never happened until the system started crashing from trying to set the secret combo flag.
Perhaps it was a result of that.
I've been in to tile pages this morning without any crashes, while having not tried to set the secret combo flag again.
I had been in the tile page quite a lot without trouble before the secret combo issue came up.

If the tile page crashes again, I'll send you a user dump.