Out of Stack Space Error

[Havie]

Hi - so have discovered I have a game killing error - out of stack space.

At first I thought it might be because I am jumping out of for next loops and I read the manual that said I needed to pop for if this is the case. I have found them all I think.

Does anyone know what else might cause this error so I can root it out! Have checked a much earlier version of my Space Invaders and I still get the error so it's been there for a while but only shows itself if you play the game through a few times.

Thanks in advance for any help you can offer.

[Daedalus]

I've never run into it myself - are you doing any sort of recursion? Jumping with Gosub without returns? Jumping out of a Select block without returning? It sounds like something's not happening in the right order, and you're just building a massive stack without clearing it.

[Havie]

Thanks - that's what I am think. Error doesn't even appear int he Blitz manual that I have! No selects but some gosubs (sorry bit old school as learnt to program from the ZX Spectrum manual).

I'll have to work my way slowly through the code - it's something that has always been there so I may be able to go back to earlier (less spaghetti) code to hunt it out!

[DamienD]

I'm sure I had this when looking at Brick Nash's Streets of Rage.

...nope, just checked, it was:

Originally Posted by DamienD

• Kept getting errors about "variable buffer to small" when testing, had to increase to "300000".

Ooops, and that was AMOS; not Blitz Basic

[Daedalus]

There's nothing wrong with a Gosub (or even a Goto, for that matter) if it's used responsibly and with good reason They're a bit old skool and can lead to difficult to debug situations, weird bugs and tricky to follow code, but they're also faster than using functions, and in game terms on stock hardware, that speed difference can be important.

Make sure every Gosub is terminated with a Return, and that if you leave the Gosub for anything, you Return back into it before Returning to the previous point. If you really need to, you can Pop out of a Gosub stack, but I think such a situation could easily be handled some other way.

[Havie]

Originally Posted by DamienD

I'm sure I had this when looking at Brick Nash's Streets of Rage.

...nope, just checked, it was:


Ooops, and that was AMOS; not Blitz Basic

Good try!

[Havie]

Originally Posted by Daedalus

There's nothing wrong with a Gosub (or even a Goto, for that matter) if it's used responsibly and with good reason They're a bit old skool and can lead to difficult to debug situations, weird bugs and tricky to follow code, but they're also faster than using functions, and in game terms on stock hardware, that speed difference can be important.

Make sure every Gosub is terminated with a Return, and that if you leave the Gosub for anything, you Return back into it before Returning to the previous point. If you really need to, you can Pop out of a Gosub stack, but I think such a situation could easily be handled some other way.

Thanks - will track them all through...