| From: | A. Timiney |
| Date: | 18 Oct 2000 at 13:01:57 |
| Subject: | Re: Stack size. |
On 16 Oct 2000, at 18:44, Curt Esser wrote:
> First, a question:
>
> If you compile and run it outside blitz with the bigger stack size,
> does it eventually crash for no apparent reason?
>
> If so, then it is an internal programming error, and you'll have to
> find it yourself, as the debugger can't catch it until you run out of
> room on the stack...
It does crash, but thats not suprising, cos I cant debug it.
>
> Probable cause for this would be exiting from a subroutine with a
> GoTo, which will leave an orphaned address on the stack every time...
>
> Another reason would be subroutines or For/Next loops nested too
> deeply.
>
> Anyway, if you are SURE these aren't the problem I think there is a
> command for specifying the stack size at the start of your program -
> problem is, I can't find it right now...
I have a feeling that its got sod all to do with stack size; after all it
'runs out' after creating 2 banks, 5 memalloc adresses, 3 256
arrays, a couple of other variables (.l type IIRC) and a couple of
nested for/next loops. It wibbles when it gets to the next for/next
loop a few lines down (which uses the same variable name as the
first loop; n)
Also, increaseing Blitz's stack size didnt help. If it should have
done, then there is most likely something else going on.
>I think there was a stack command in StatsFuncs, in dev/basic on
>Aminet...if
>not, gimme a shout and I'll dig out the code...unless someone else
>already
>has it handy...?
The function in there is for launching WB programs.
Ta ra,
-Alex T
---------------------------------------------------------------------
To unsubscribe, e-mail: blitz-list-unsubscribe@netsoc.ucd.ie
For additional commands, e-mail: blitz-list-help@netsoc.ucd.ie